Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de9d1466f7b3304fbc5ba92113ed83f4e0dd3b0938e797976f30b44467c514d6

Tx prefix hash: f4fe691a2bc3652a3a377bff24d365428f7994fc3748897cffbbb89c401b73e6
Tx public key: a03d1d639732bd5b83a0e56d835e6c6c6abf483ce4fad7460cc562710cdb0481
Timestamp: 1737306922 Timestamp [UCT]: 2025-01-19 17:15:22 Age [y:d:h:m:s]: 00:331:12:13:45
Block: 1200852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234504 RingCT/type: yes/0
Extra: 01a03d1d639732bd5b83a0e56d835e6c6c6abf483ce4fad7460cc562710cdb0481021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e0263307518a917088efb38d9f457fc4535f6d34e4c0bd1f062458ee3feb83e 0.600000000000 1687499 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": 1200862, "vin": [ { "gen": { "height": 1200852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e0263307518a917088efb38d9f457fc4535f6d34e4c0bd1f062458ee3feb83e" } } ], "extra": [ 1, 160, 61, 29, 99, 151, 50, 189, 91, 131, 160, 229, 109, 131, 94, 108, 108, 106, 191, 72, 60, 228, 250, 215, 70, 12, 197, 98, 113, 12, 219, 4, 129, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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