Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 807e12600a82af989ba3cc88f1ff11a3d084a202373d2395d86b4eaa33519e56

Tx prefix hash: 8e420302524d70a7ae13283a0bf89199b4050b8c961a0c139af4a868b5022008
Tx public key: d2f8204902fb1ca43014476cbf3245abed0e7dc915fce48d3e19707e1de48942
Timestamp: 1713897282 Timestamp [UCT]: 2024-04-23 18:34:42 Age [y:d:h:m:s]: 01:023:01:12:01
Block: 1006964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277419 RingCT/type: yes/0
Extra: 01d2f8204902fb1ca43014476cbf3245abed0e7dc915fce48d3e19707e1de489420211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 831c9e3b4619da9b7ff786f05e618dc4a68ca5830d88788363d803c3c7c62072 0.600000000000 1468162 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": 1006974, "vin": [ { "gen": { "height": 1006964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "831c9e3b4619da9b7ff786f05e618dc4a68ca5830d88788363d803c3c7c62072" } } ], "extra": [ 1, 210, 248, 32, 73, 2, 251, 28, 164, 48, 20, 71, 108, 191, 50, 69, 171, 237, 14, 125, 201, 21, 252, 228, 141, 62, 25, 112, 126, 29, 228, 137, 66, 2, 17, 0, 0, 0, 3, 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