Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1724b56d199f18e68c1b15ced837296d8270fd795314da1d3f1e6983060dd5c8

Tx prefix hash: 1ddeaa13e407315f636457cef14392a731d3585dc9bb8d66697d2847cdf6dd3d
Tx public key: 3d329a79ea8dbd73625e7eb8c20194da996b48a91e8eee2ec8f360f8f915d428
Timestamp: 1703771058 Timestamp [UCT]: 2023-12-28 13:44:18 Age [y:d:h:m:s]: 01:137:04:45:00
Block: 923005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359201 RingCT/type: yes/0
Extra: 013d329a79ea8dbd73625e7eb8c20194da996b48a91e8eee2ec8f360f8f915d42802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e98e7d367d86186f7694d286fb9352d3d96de13bccbf046553c7c597d1e0617e 0.600000000000 1380711 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": 923015, "vin": [ { "gen": { "height": 923005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e98e7d367d86186f7694d286fb9352d3d96de13bccbf046553c7c597d1e0617e" } } ], "extra": [ 1, 61, 50, 154, 121, 234, 141, 189, 115, 98, 94, 126, 184, 194, 1, 148, 218, 153, 107, 72, 169, 30, 142, 238, 46, 200, 243, 96, 248, 249, 21, 212, 40, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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