Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0381a707b96c502ca972051e318a52228ba4f091b01e6178589eee4c8a8a9cdf

Tx prefix hash: 4d09c0a3edb14b19e13d8efb75a7553c8880aae0837eac999e9d310bec639e91
Tx public key: 149c7f07df2f7ef120222b050d601cc5ff3ce94920828a6c3ac0baa901241e89
Timestamp: 1731740207 Timestamp [UCT]: 2024-11-16 06:56:47 Age [y:d:h:m:s]: 00:194:07:02:47
Block: 1154806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138726 RingCT/type: yes/0
Extra: 01149c7f07df2f7ef120222b050d601cc5ff3ce94920828a6c3ac0baa901241e89021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6a054db3a0620d7bdfb9d000f62624a8d1b56dc8d795ce647ddb69d9c1f7935 0.600000000000 1640419 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": 1154816, "vin": [ { "gen": { "height": 1154806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6a054db3a0620d7bdfb9d000f62624a8d1b56dc8d795ce647ddb69d9c1f7935" } } ], "extra": [ 1, 20, 156, 127, 7, 223, 47, 126, 241, 32, 34, 43, 5, 13, 96, 28, 197, 255, 60, 233, 73, 32, 130, 138, 108, 58, 192, 186, 169, 1, 36, 30, 137, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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