Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4e900de3f711c53349a5808eca12fd89aec5d5ab771e17ac0d0de62d808c8f3

Tx prefix hash: 2a2ed62a6b15584e77b3e49b0e742f0e5248b2b9e75bdb6e51793ea6366fc0e9
Tx public key: 53499fd39693ff4fbd1b79c57322e0ac829fa0f36357a33c7fe8b657256ec5f0
Timestamp: 1712398925 Timestamp [UCT]: 2024-04-06 10:22:05 Age [y:d:h:m:s]: 01:207:07:27:18
Block: 994512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406860 RingCT/type: yes/0
Extra: 0153499fd39693ff4fbd1b79c57322e0ac829fa0f36357a33c7fe8b657256ec5f00211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57067ec9de01e36867272d2ed84745011a1f777b5a27641cff7ee99f31d34ce3 0.600000000000 1454916 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": 994522, "vin": [ { "gen": { "height": 994512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57067ec9de01e36867272d2ed84745011a1f777b5a27641cff7ee99f31d34ce3" } } ], "extra": [ 1, 83, 73, 159, 211, 150, 147, 255, 79, 189, 27, 121, 197, 115, 34, 224, 172, 130, 159, 160, 243, 99, 87, 163, 60, 127, 232, 182, 87, 37, 110, 197, 240, 2, 17, 0, 0, 0, 1, 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