Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a7dc76fad253fd9c3cc896da37e8499085492e508ed1895f14bef971b9d1bb4

Tx prefix hash: 598179b07417d0738e0e4c10300a37cc4c50616b1d1b7453772b25a42da0fc7e
Tx public key: d541f49c6e0927191e242901dd8065cbcb074b039896b8e4e5828d26df479311
Timestamp: 1577836314 Timestamp [UCT]: 2019-12-31 23:51:54 Age [y:d:h:m:s]: 04:362:08:52:50
Block: 36059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148122 RingCT/type: yes/0
Extra: 01d541f49c6e0927191e242901dd8065cbcb074b039896b8e4e5828d26df47931102110000016e4ac5aa02000000000000000000

1 output(s) for total of 466.146489137000 dcy

stealth address amount amount idx
00: 058a6e5695e9c6cf97f410ab5528c81383f9348027d210b15ae72213464db3b1 466.146489137000 60947 of 0

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": 36069, "vin": [ { "gen": { "height": 36059 } } ], "vout": [ { "amount": 466146489137, "target": { "key": "058a6e5695e9c6cf97f410ab5528c81383f9348027d210b15ae72213464db3b1" } } ], "extra": [ 1, 213, 65, 244, 156, 110, 9, 39, 25, 30, 36, 41, 1, 221, 128, 101, 203, 203, 7, 75, 3, 152, 150, 184, 228, 229, 130, 141, 38, 223, 71, 147, 17, 2, 17, 0, 0, 1, 110, 74, 197, 170, 2, 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