Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21100d71818d0b8c7cb744e74e95e40a12e99a885a387bc3cc6823022aba75d3

Tx prefix hash: 15dadf3b06bc96049a3d4ecd67b0abf4ee7fccf9b1b72630d83ebcd5802aae56
Tx public key: 2be974c7f5e7e450fb72c880e9ef59a3496877254088dfcb6d9d24091450d05b
Timestamp: 1730438269 Timestamp [UCT]: 2024-11-01 05:17:49 Age [y:d:h:m:s]: 00:152:18:03:51
Block: 1144006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109000 RingCT/type: yes/0
Extra: 012be974c7f5e7e450fb72c880e9ef59a3496877254088dfcb6d9d24091450d05b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1656e49cd560d5c6fcc3491fbb6bc9f9556e3a0002425328a21fdfc63c68a2b9 0.600000000000 1628069 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": 1144016, "vin": [ { "gen": { "height": 1144006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1656e49cd560d5c6fcc3491fbb6bc9f9556e3a0002425328a21fdfc63c68a2b9" } } ], "extra": [ 1, 43, 233, 116, 199, 245, 231, 228, 80, 251, 114, 200, 128, 233, 239, 89, 163, 73, 104, 119, 37, 64, 136, 223, 203, 109, 157, 36, 9, 20, 80, 208, 91, 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