Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9627216c063400b68a8bb0939364d296b963eb4a557e07dc6fd09b78bb9716fd

Tx prefix hash: 7a5ce71d96fad90244accc1daeb0f8f287649750876292a75f8dbb5d936a11f9
Tx public key: 1143f9111581007f2d9c7d320a9ef478d010ed5329fc7e212a1c8cfcfc1d4d24
Timestamp: 1726928153 Timestamp [UCT]: 2024-09-21 14:15:53 Age [y:d:h:m:s]: 00:186:00:35:11
Block: 1114996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132744 RingCT/type: yes/0
Extra: 011143f9111581007f2d9c7d320a9ef478d010ed5329fc7e212a1c8cfcfc1d4d240211000000022c3a34dc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4099f68059aa59c68573aa9a6874a44e018e321a4d5717808e92142b8b24f1f9 0.600000000000 1594973 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": 1115006, "vin": [ { "gen": { "height": 1114996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4099f68059aa59c68573aa9a6874a44e018e321a4d5717808e92142b8b24f1f9" } } ], "extra": [ 1, 17, 67, 249, 17, 21, 129, 0, 127, 45, 156, 125, 50, 10, 158, 244, 120, 208, 16, 237, 83, 41, 252, 126, 33, 42, 28, 140, 252, 252, 29, 77, 36, 2, 17, 0, 0, 0, 2, 44, 58, 52, 220, 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