Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 633b4af97b061225570e17da931c07ffec21c1f5b070a5d67258cd4fb691f1ce

Tx prefix hash: b1263b897e4def3210d086b1a7fe5aa9bb1d3eb61410b2a4423ea4cd7d35367c
Tx public key: d94db1925904fbda43aabebde74d09fd0932edf47004f603e592ae3592bf5486
Timestamp: 1732661509 Timestamp [UCT]: 2024-11-26 22:51:49 Age [y:d:h:m:s]: 00:112:11:46:44
Block: 1162427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80221 RingCT/type: yes/0
Extra: 01d94db1925904fbda43aabebde74d09fd0932edf47004f603e592ae3592bf54860211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36d000d84bd9bbea2b53e29144a20b921f74e564bcb241d254fc315fb3176c4f 0.600000000000 1648082 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": 1162437, "vin": [ { "gen": { "height": 1162427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36d000d84bd9bbea2b53e29144a20b921f74e564bcb241d254fc315fb3176c4f" } } ], "extra": [ 1, 217, 77, 177, 146, 89, 4, 251, 218, 67, 170, 190, 189, 231, 77, 9, 253, 9, 50, 237, 244, 112, 4, 246, 3, 229, 146, 174, 53, 146, 191, 84, 134, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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