Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bb9d5e2a3df34faff8be79fbdefa674d604fe35514dee6831010dddd4248cec

Tx prefix hash: f032a34d1c96301c1eb775356a10c6185de3467a331fea42884d44f2f790b4d1
Tx public key: e9df32b7d2e7a37e69033b37994e4cd813373fdcbc70d9da31f19a7d79ba129c
Timestamp: 1715023216 Timestamp [UCT]: 2024-05-06 19:20:16 Age [y:d:h:m:s]: 01:032:13:02:35
Block: 1016299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284206 RingCT/type: yes/0
Extra: 01e9df32b7d2e7a37e69033b37994e4cd813373fdcbc70d9da31f19a7d79ba129c02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e86c580832971abd92029cfd3ada0d87232295778dff625fbf35c70edc2afd1 0.600000000000 1479842 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": 1016309, "vin": [ { "gen": { "height": 1016299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e86c580832971abd92029cfd3ada0d87232295778dff625fbf35c70edc2afd1" } } ], "extra": [ 1, 233, 223, 50, 183, 210, 231, 163, 126, 105, 3, 59, 55, 153, 78, 76, 216, 19, 55, 63, 220, 188, 112, 217, 218, 49, 241, 154, 125, 121, 186, 18, 156, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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