Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e3a38d582d49aa35478820167637f758d5f0b622c0ae9b5900f5142efc98840

Tx prefix hash: 94d34e9b24b5bc12ea72f32ae65be46949c292c8a1ca0ae29360cbde16659869
Tx public key: 961d6348e54106aa27d32be7c711eb6bd13defdec48d4c2782340c3e999d8030
Timestamp: 1711157764 Timestamp [UCT]: 2024-03-23 01:36:04 Age [y:d:h:m:s]: 00:339:10:32:53
Block: 984267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242654 RingCT/type: yes/0
Extra: 01961d6348e54106aa27d32be7c711eb6bd13defdec48d4c2782340c3e999d80300211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9d8083803f86c1f7e8c3727cb5bd101fd32dd8a9774c1a43af51ab9fd787e5d 0.600000000000 1444436 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": 984277, "vin": [ { "gen": { "height": 984267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9d8083803f86c1f7e8c3727cb5bd101fd32dd8a9774c1a43af51ab9fd787e5d" } } ], "extra": [ 1, 150, 29, 99, 72, 229, 65, 6, 170, 39, 211, 43, 231, 199, 17, 235, 107, 209, 61, 239, 222, 196, 141, 76, 39, 130, 52, 12, 62, 153, 157, 128, 48, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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