Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b0bdca45a3cdbfbf47f7e71822b83987d42f01a79af76fd3c868aed78f37de2

Tx prefix hash: f88649795317e62738b4d5c4c3c3bbb21e7d5afde394ae94852eb7eb9b13114a
Tx public key: 61a6c3a782f04bbdf8b0099fb5ed75cebefc8dc4a9c4d02f68258f8dba2e0445
Timestamp: 1694295905 Timestamp [UCT]: 2023-09-09 21:45:05 Age [y:d:h:m:s]: 01:248:00:25:44
Block: 844641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438396 RingCT/type: yes/0
Extra: 0161a6c3a782f04bbdf8b0099fb5ed75cebefc8dc4a9c4d02f68258f8dba2e044502110000000675e3f0e9000000000000000000

1 output(s) for total of 0.975784251000 dcy

stealth address amount amount idx
00: c222a4cc08ddc965a34bdc9db93f988a6fb955fcd252dcd77cb5bc139e81a18b 0.975784251000 1297963 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": 844651, "vin": [ { "gen": { "height": 844641 } } ], "vout": [ { "amount": 975784251, "target": { "key": "c222a4cc08ddc965a34bdc9db93f988a6fb955fcd252dcd77cb5bc139e81a18b" } } ], "extra": [ 1, 97, 166, 195, 167, 130, 240, 75, 189, 248, 176, 9, 159, 181, 237, 117, 206, 190, 252, 141, 196, 169, 196, 208, 47, 104, 37, 143, 141, 186, 46, 4, 69, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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