Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d98bd32f1096d4f4def7eb95ae22fb0d69da3b233c3265661d4d908f4613f94

Tx prefix hash: 6544cb2befe80c41a0a21843cfc4f07720b9bbe9fa8fafbf8156a3bccc87f7c9
Tx public key: 980316d8fa941daa3ca379e5efdc58f4137ff0abdb63dd4202fea8be57e85603
Timestamp: 1677865000 Timestamp [UCT]: 2023-03-03 17:36:40 Age [y:d:h:m:s]: 02:001:00:04:33
Block: 709124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522263 RingCT/type: yes/0
Extra: 01980316d8fa941daa3ca379e5efdc58f4137ff0abdb63dd4202fea8be57e856030211000000025029cbac000000000000000000

1 output(s) for total of 2.743959623000 dcy

stealth address amount amount idx
00: e9aef28c200a37fcdabc0cae74d3fe1ec6253a1c2abed83eb8bd8a247408c8f4 2.743959623000 1153077 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": 709134, "vin": [ { "gen": { "height": 709124 } } ], "vout": [ { "amount": 2743959623, "target": { "key": "e9aef28c200a37fcdabc0cae74d3fe1ec6253a1c2abed83eb8bd8a247408c8f4" } } ], "extra": [ 1, 152, 3, 22, 216, 250, 148, 29, 170, 60, 163, 121, 229, 239, 220, 88, 244, 19, 127, 240, 171, 219, 99, 221, 66, 2, 254, 168, 190, 87, 232, 86, 3, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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