Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6a5fbd0333cfb25374bd237e2adcacb5c0c9e99e84ad5ad64cb34a5cbb6fe01

Tx prefix hash: d9aad017c3908a0ae703ebc27601ec83792aed1b457a773b04135069ef598ff3
Tx public key: 684d89c4bcb90544fa4aca0fda10cac19ec8e01d2e9442f3b59d0bda996c0368
Timestamp: 1721159092 Timestamp [UCT]: 2024-07-16 19:44:52 Age [y:d:h:m:s]: 00:284:13:08:02
Block: 1067177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203295 RingCT/type: yes/0
Extra: 01684d89c4bcb90544fa4aca0fda10cac19ec8e01d2e9442f3b59d0bda996c036802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a300ccca74e8e9ee2a35eaff9190ed667aabe9b2e74ddec10629d419ffed2ae9 0.600000000000 1537920 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": 1067187, "vin": [ { "gen": { "height": 1067177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a300ccca74e8e9ee2a35eaff9190ed667aabe9b2e74ddec10629d419ffed2ae9" } } ], "extra": [ 1, 104, 77, 137, 196, 188, 185, 5, 68, 250, 74, 202, 15, 218, 16, 202, 193, 158, 200, 224, 29, 46, 148, 66, 243, 181, 157, 11, 218, 153, 108, 3, 104, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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