Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d3731ebec60efabf968fb4d356ec785a9538a6043652d4d585c117b77f0ad62

Tx prefix hash: fb64be54cb4bd4ac0447c792a56440f5e8a665eae1766705a1c383f4a6a84d2e
Tx public key: 464ed3c2766ebace077b99e82ab58073cc54e3c82c0c0707b4febf3e7a18ff62
Timestamp: 1758064456 Timestamp [UCT]: 2025-09-16 23:14:16 Age [y:d:h:m:s]: 00:056:10:00:57
Block: 1370008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40402 RingCT/type: yes/0
Extra: 01464ed3c2766ebace077b99e82ab58073cc54e3c82c0c0707b4febf3e7a18ff62021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 770900f3a4ea4555be3021c8bac4d217074a663e79cf3b7e8981b062a06e78d9 0.600000000000 1858083 of 15

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": 1370018, "vin": [ { "gen": { "height": 1370008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "770900f3a4ea4555be3021c8bac4d217074a663e79cf3b7e8981b062a06e78d9" } } ], "extra": [ 1, 70, 78, 211, 194, 118, 110, 186, 206, 7, 123, 153, 232, 42, 181, 128, 115, 204, 84, 227, 200, 44, 12, 7, 7, 180, 254, 191, 62, 122, 24, 255, 98, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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