Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 924fee973b18bb1da76b180de4b27cfd75ee9494715c5f184e48f48d876b4390

Tx prefix hash: 96b93779da32e7cfadf10752ee48d4d1c7009a314bc5f5af32993ec91496963e
Tx public key: e3b986734e071d99e61358994bc9e6cd2a1cbf56874861e9c1c74df12e13e30c
Timestamp: 1714503224 Timestamp [UCT]: 2024-04-30 18:53:44 Age [y:d:h:m:s]: 00:252:03:19:32
Block: 1011990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180463 RingCT/type: yes/0
Extra: 01e3b986734e071d99e61358994bc9e6cd2a1cbf56874861e9c1c74df12e13e30c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8336f943c4cd033a829e449a8aef964a6f551371c9447640b8aedf294c1d5b5 0.600000000000 1474372 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": 1012000, "vin": [ { "gen": { "height": 1011990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8336f943c4cd033a829e449a8aef964a6f551371c9447640b8aedf294c1d5b5" } } ], "extra": [ 1, 227, 185, 134, 115, 78, 7, 29, 153, 230, 19, 88, 153, 75, 201, 230, 205, 42, 28, 191, 86, 135, 72, 97, 233, 193, 199, 77, 241, 46, 19, 227, 12, 2, 17, 0, 0, 0, 2, 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