Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a65b1d05fd34e7e63d844afb9bc1e1ed9619f12c5960667673dbd521d543b39b

Tx prefix hash: 4b4c4498c4f09692fd0d667dbdbdaba525ea95cb88c48a90acbe524e7ecb93e4
Tx public key: ee4b6f9d0f36a1f77a05521f5fadce6db96981a3b3eddc1de51c970f07b7be3f
Timestamp: 1708965262 Timestamp [UCT]: 2024-02-26 16:34:22 Age [y:d:h:m:s]: 01:112:20:30:09
Block: 966079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341584 RingCT/type: yes/0
Extra: 01ee4b6f9d0f36a1f77a05521f5fadce6db96981a3b3eddc1de51c970f07b7be3f0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbee75d54db4a3583da7f7e52297df532df6ef3dc24255047994e12fa1822e7c 0.600000000000 1425836 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": 966089, "vin": [ { "gen": { "height": 966079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbee75d54db4a3583da7f7e52297df532df6ef3dc24255047994e12fa1822e7c" } } ], "extra": [ 1, 238, 75, 111, 157, 15, 54, 161, 247, 122, 5, 82, 31, 95, 173, 206, 109, 185, 105, 129, 163, 179, 237, 220, 29, 229, 28, 151, 15, 7, 183, 190, 63, 2, 17, 0, 0, 0, 3, 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