Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20ec737128f8d307ed0b13eb827c6cd2be00dc75db4f7cd5c73233b35148520c

Tx prefix hash: bc6616259005c9fee4c6d53fcb52455ced9057f98fa25b353551fb7826eff8d0
Tx public key: 68e72b91ab8466979a1d7d5462602ad8fc67e502bf5ec3fcd0c9e6771f65eeb6
Timestamp: 1711224358 Timestamp [UCT]: 2024-03-23 20:05:58 Age [y:d:h:m:s]: 01:229:20:19:07
Block: 984824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422943 RingCT/type: yes/0
Extra: 0168e72b91ab8466979a1d7d5462602ad8fc67e502bf5ec3fcd0c9e6771f65eeb60211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc8ae1edf0e0d913f6a48d5e1474aa6eb796a7a4181f8f53ab207b2656465786 0.600000000000 1444997 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": 984834, "vin": [ { "gen": { "height": 984824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc8ae1edf0e0d913f6a48d5e1474aa6eb796a7a4181f8f53ab207b2656465786" } } ], "extra": [ 1, 104, 231, 43, 145, 171, 132, 102, 151, 154, 29, 125, 84, 98, 96, 42, 216, 252, 103, 229, 2, 191, 94, 195, 252, 208, 201, 230, 119, 31, 101, 238, 182, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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