Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9add7bfad7866fc5f9e4e0ee13dbbb120378f0072862b9a1f28f4a51ff68f19

Tx prefix hash: 8e985dc080bde9814a6abbc564cb9ec7320b74679d80084dc730b942861624d7
Tx public key: 039b827801db4568df8ee9003480a47fddb98aa935b5a5c081a787d984f5d9fa
Timestamp: 1737100729 Timestamp [UCT]: 2025-01-17 07:58:49 Age [y:d:h:m:s]: 00:152:10:37:46
Block: 1199179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108648 RingCT/type: yes/0
Extra: 01039b827801db4568df8ee9003480a47fddb98aa935b5a5c081a787d984f5d9fa021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0ddeaec679be9dcd9bda4529f9fbde850668b47cec5870a4495650872d875b1 0.600000000000 1685808 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": 1199189, "vin": [ { "gen": { "height": 1199179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0ddeaec679be9dcd9bda4529f9fbde850668b47cec5870a4495650872d875b1" } } ], "extra": [ 1, 3, 155, 130, 120, 1, 219, 69, 104, 223, 142, 233, 0, 52, 128, 164, 127, 221, 185, 138, 169, 53, 181, 165, 192, 129, 167, 135, 217, 132, 245, 217, 250, 2, 17, 0, 0, 0, 5, 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