Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38f210ddbdbef089c3ccd592779d5ca8c6ea39ed3a3e4f12d2d5b9c2e1c17560

Tx prefix hash: dae152741e6379677e81d107a069d91fbd5ecdfce4991d2c05f97987c091abb4
Tx public key: fb99598c497b600dab092114ec8302a74c89b2256329d24b9d7033398aa18727
Timestamp: 1698673305 Timestamp [UCT]: 2023-10-30 13:41:45 Age [y:d:h:m:s]: 02:007:07:59:10
Block: 880960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524801 RingCT/type: yes/0
Extra: 01fb99598c497b600dab092114ec8302a74c89b2256329d24b9d7033398aa18727021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.739628824000 dcy

stealth address amount amount idx
00: f8e7fa66e015041ae34744aa6c3bde1ee70dc461a3694a5ec3521aef1d04859e 0.739628824000 1336530 of 0

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": 880970, "vin": [ { "gen": { "height": 880960 } } ], "vout": [ { "amount": 739628824, "target": { "key": "f8e7fa66e015041ae34744aa6c3bde1ee70dc461a3694a5ec3521aef1d04859e" } } ], "extra": [ 1, 251, 153, 89, 140, 73, 123, 96, 13, 171, 9, 33, 20, 236, 131, 2, 167, 76, 137, 178, 37, 99, 41, 210, 75, 157, 112, 51, 57, 138, 161, 135, 39, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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