Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65eff7a0e0e4cef11aabd6519d327666edb388718a66d9dfa6b65b474ee9fa73

Tx prefix hash: 3a635c2fba4a8bc091e479b43749c33afbb162d89994061a412cceaa058353b4
Tx public key: 3a21a24a78e72b5d785c98ca022fde783420a3b98c13063b3625df04fdb1656d
Timestamp: 1697012507 Timestamp [UCT]: 2023-10-11 08:21:47 Age [y:d:h:m:s]: 01:180:12:51:32
Block: 867180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390060 RingCT/type: yes/0
Extra: 013a21a24a78e72b5d785c98ca022fde783420a3b98c13063b3625df04fdb1656d02110000000833af99f4000000000000000000

1 output(s) for total of 0.821623227000 dcy

stealth address amount amount idx
00: f1af77468883f3b46f7ee74a4e65975b2098d22bf7204c911ab59097e295b2ae 0.821623227000 1321838 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": 867190, "vin": [ { "gen": { "height": 867180 } } ], "vout": [ { "amount": 821623227, "target": { "key": "f1af77468883f3b46f7ee74a4e65975b2098d22bf7204c911ab59097e295b2ae" } } ], "extra": [ 1, 58, 33, 162, 74, 120, 231, 43, 93, 120, 92, 152, 202, 2, 47, 222, 120, 52, 32, 163, 185, 140, 19, 6, 59, 54, 37, 223, 4, 253, 177, 101, 109, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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