Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 641d6aef816cd96f4e26d312fd8c00a30662ce2a6414f6676b10774777b955eb

Tx prefix hash: c2524546bf73da273a26751cc6b11b6c3ae8257a283e5eff32ee67915106a08b
Tx public key: decc1b0ddde263e7e3df6b75aa4511beec876442cb0dabc948c3417e8b47629f
Timestamp: 1750797592 Timestamp [UCT]: 2025-06-24 20:39:52 Age [y:d:h:m:s]: 00:194:10:44:57
Block: 1312057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136977 RingCT/type: yes/0
Extra: 01decc1b0ddde263e7e3df6b75aa4511beec876442cb0dabc948c3417e8b47629f021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8503ba9d52296c4811f4223237b34958e719ac5a2e74086db3ea602e07d4665 0.600000000000 1799688 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": 1312067, "vin": [ { "gen": { "height": 1312057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8503ba9d52296c4811f4223237b34958e719ac5a2e74086db3ea602e07d4665" } } ], "extra": [ 1, 222, 204, 27, 13, 221, 226, 99, 231, 227, 223, 107, 117, 170, 69, 17, 190, 236, 135, 100, 66, 203, 13, 171, 201, 72, 195, 65, 126, 139, 71, 98, 159, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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