Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df84f9361d93692c7db6ca7c7b88a6219e71a5ad0e8460da2f996671826e6f02

Tx prefix hash: 79f12d21b7f7163909d019109e3ba03f09f437f487508b7bf2d11776df49e8f5
Tx public key: 62a59513905368b21f4c13383a3036fd1ab05984ca9a7e7ed5d4734b4d6df924
Timestamp: 1710283313 Timestamp [UCT]: 2024-03-12 22:41:53 Age [y:d:h:m:s]: 01:072:03:12:09
Block: 977010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312580 RingCT/type: yes/0
Extra: 0162a59513905368b21f4c13383a3036fd1ab05984ca9a7e7ed5d4734b4d6df9240211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 618f0e8b5e794a83b70c53d029a52009fc184a0c5d78b1bc89a62fd30ff8a087 0.600000000000 1437011 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": 977020, "vin": [ { "gen": { "height": 977010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "618f0e8b5e794a83b70c53d029a52009fc184a0c5d78b1bc89a62fd30ff8a087" } } ], "extra": [ 1, 98, 165, 149, 19, 144, 83, 104, 178, 31, 76, 19, 56, 58, 48, 54, 253, 26, 176, 89, 132, 202, 154, 126, 126, 213, 212, 115, 75, 77, 109, 249, 36, 2, 17, 0, 0, 0, 8, 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