Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 632a4602540f90aaf7d4d0e3baa1e7d23aa022c1abef2576ff43b6933e44bb5b

Tx prefix hash: 67f6b11cb4a8e4fc55c5f2a8085dbb1a9b1e12fcd03f4969ff28015212f8ca14
Tx public key: 850179e1f7cd309e84eff56b8c6e2134d8b0fec95f3c3d86d4b040018dffed30
Timestamp: 1631475007 Timestamp [UCT]: 2021-09-12 19:30:07 Age [y:d:h:m:s]: 04:049:11:32:17
Block: 332479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1069288 RingCT/type: yes/0
Extra: 01850179e1f7cd309e84eff56b8c6e2134d8b0fec95f3c3d86d4b040018dffed300211000000245d7cc334000000000000000000

1 output(s) for total of 48.569037526000 dcy

stealth address amount amount idx
00: 2e8055848fee2a5515c68c72013be71e5d6fbbd9d0f84651e745a4b1614f3fa2 48.569037526000 686546 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 332489, "vin": [ { "gen": { "height": 332479 } } ], "vout": [ { "amount": 48569037526, "target": { "key": "2e8055848fee2a5515c68c72013be71e5d6fbbd9d0f84651e745a4b1614f3fa2" } } ], "extra": [ 1, 133, 1, 121, 225, 247, 205, 48, 158, 132, 239, 245, 107, 140, 110, 33, 52, 216, 176, 254, 201, 95, 60, 61, 134, 212, 176, 64, 1, 141, 255, 237, 48, 2, 17, 0, 0, 0, 36, 93, 124, 195, 52, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8