Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99fdf8cc3bca9d7412487cec30d6996a263c932e01516743761e70f6b2dbcd41

Tx prefix hash: 764b9b2c5cad9b383b731685e491786d42eb347903c842c95d6b2759d7b57a8a
Tx public key: 0f0310f8f80ec103a0777ddf9137aed9e73a44b72ccbb53f43c9f6b4d373d446
Timestamp: 1722004858 Timestamp [UCT]: 2024-07-26 14:40:58 Age [y:d:h:m:s]: 00:244:11:02:36
Block: 1074184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174615 RingCT/type: yes/0
Extra: 010f0310f8f80ec103a0777ddf9137aed9e73a44b72ccbb53f43c9f6b4d373d44602110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b03789704bd4bd7e9b153dc237e7bf8d14643ec6fe7f5ce86a28a90585cae554 0.600000000000 1546697 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": 1074194, "vin": [ { "gen": { "height": 1074184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b03789704bd4bd7e9b153dc237e7bf8d14643ec6fe7f5ce86a28a90585cae554" } } ], "extra": [ 1, 15, 3, 16, 248, 248, 14, 193, 3, 160, 119, 125, 223, 145, 55, 174, 217, 231, 58, 68, 183, 44, 203, 181, 63, 67, 201, 246, 180, 211, 115, 212, 70, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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