Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb955e19f4eea88c4faf1a0c610cfba19f881b97a3e936ae9e681766a6bab37c

Tx prefix hash: 57eed2c1c04b1a7f94e509c8eaa989f22a8234ff6eec6253118fa2dc2ba11f8f
Tx public key: 6536cfd3884b978b3533ecd90dca2df89090efc22155b341055b1d468c371739
Timestamp: 1726854138 Timestamp [UCT]: 2024-09-20 17:42:18 Age [y:d:h:m:s]: 00:055:06:23:54
Block: 1114382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39504 RingCT/type: yes/0
Extra: 016536cfd3884b978b3533ecd90dca2df89090efc22155b341055b1d468c371739021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 801e033684d89b1d410684caaa546bd4e71012c49fec5bae3acc0ea9bac3bebd 0.600000000000 1594183 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": 1114392, "vin": [ { "gen": { "height": 1114382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "801e033684d89b1d410684caaa546bd4e71012c49fec5bae3acc0ea9bac3bebd" } } ], "extra": [ 1, 101, 54, 207, 211, 136, 75, 151, 139, 53, 51, 236, 217, 13, 202, 45, 248, 144, 144, 239, 194, 33, 85, 179, 65, 5, 91, 29, 70, 140, 55, 23, 57, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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