Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47c0f3ff997ef79dec5db4d6f454e2df5dff6d25126287bd04292cd6102213b8

Tx prefix hash: 4e3eed655938aeaa1c2d8d217b15572d1b6ba12a6874766e80467f0fe41064df
Tx public key: 65172d661c062c57905afcaffcbd4a1c3efa10ad073df89c1071856a627fdce7
Timestamp: 1733020914 Timestamp [UCT]: 2024-12-01 02:41:54 Age [y:d:h:m:s]: 00:113:21:40:28
Block: 1165410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81197 RingCT/type: yes/0
Extra: 0165172d661c062c57905afcaffcbd4a1c3efa10ad073df89c1071856a627fdce70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8753e779816f0ba45e2d46f76caa91a62cda32035d2621edef2d256995e0d7b7 0.600000000000 1651085 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": 1165420, "vin": [ { "gen": { "height": 1165410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8753e779816f0ba45e2d46f76caa91a62cda32035d2621edef2d256995e0d7b7" } } ], "extra": [ 1, 101, 23, 45, 102, 28, 6, 44, 87, 144, 90, 252, 175, 252, 189, 74, 28, 62, 250, 16, 173, 7, 61, 248, 156, 16, 113, 133, 106, 98, 127, 220, 231, 2, 17, 0, 0, 0, 3, 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