Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65b389fb486adccc981e2033d408c5475e128f500f5b83db4d7cc85d5b9f4eb8

Tx prefix hash: b18b6720aa3508d1fcd50912ba4432734a1de7224be8cfd46ba977b482d8eb7c
Tx public key: 63af5c588788ce579d0b75a062e957f2f1321c56c41cd6346efd13564df56a30
Timestamp: 1702273439 Timestamp [UCT]: 2023-12-11 05:43:59 Age [y:d:h:m:s]: 01:334:05:04:53
Block: 910592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497724 RingCT/type: yes/0
Extra: 0163af5c588788ce579d0b75a062e957f2f1321c56c41cd6346efd13564df56a30021100000011faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df1a47014f864041a7dec409aca70ee74e91fe1d4e0ddd3cb7ef71d67e0c6e0b 0.600000000000 1367753 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": 910602, "vin": [ { "gen": { "height": 910592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df1a47014f864041a7dec409aca70ee74e91fe1d4e0ddd3cb7ef71d67e0c6e0b" } } ], "extra": [ 1, 99, 175, 92, 88, 135, 136, 206, 87, 157, 11, 117, 160, 98, 233, 87, 242, 241, 50, 28, 86, 196, 28, 214, 52, 110, 253, 19, 86, 77, 245, 106, 48, 2, 17, 0, 0, 0, 17, 250, 243, 92, 156, 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