Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c1ec31019e9a3624c51ecd0c52451119db20a8d4893528dbdeeac402e67c396

Tx prefix hash: fd14033b4a9aed6ce4a4914ee665137aafa3904d64567125b2e4a3ba25887824
Tx public key: 4ab210162e8081e8d2b4dbf03250693ad2d5973264e2358243a4a3ea6d3c305a
Timestamp: 1702945693 Timestamp [UCT]: 2023-12-19 00:28:13 Age [y:d:h:m:s]: 01:185:10:24:20
Block: 916170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393536 RingCT/type: yes/0
Extra: 014ab210162e8081e8d2b4dbf03250693ad2d5973264e2358243a4a3ea6d3c305a021100000007faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ade8fccef0d07ec416a48206209a5a52803b60585b0d751d09f4cac837ef8e6 0.600000000000 1373652 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": 916180, "vin": [ { "gen": { "height": 916170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ade8fccef0d07ec416a48206209a5a52803b60585b0d751d09f4cac837ef8e6" } } ], "extra": [ 1, 74, 178, 16, 22, 46, 128, 129, 232, 210, 180, 219, 240, 50, 80, 105, 58, 210, 213, 151, 50, 100, 226, 53, 130, 67, 164, 163, 234, 109, 60, 48, 90, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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