Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2f0d263d4fc3303d2fdff0bd913bfe5f57fd381e14fe21dd5d7ec0375303a37

Tx prefix hash: 7687e59b07fb27d02b8c6ab2b9685e744290265054915f8acc774880f984197a
Tx public key: b7485cbd24cdb982a2b1f0aea956daa21768a83eb385fa2b320e7f6ad4241604
Timestamp: 1737491618 Timestamp [UCT]: 2025-01-21 20:33:38 Age [y:d:h:m:s]: 00:147:23:46:45
Block: 1202368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105514 RingCT/type: yes/0
Extra: 01b7485cbd24cdb982a2b1f0aea956daa21768a83eb385fa2b320e7f6ad4241604021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6874c67df169940c359b45dc749091e5d365a8a89956ea141c4d0d637aa48392 0.600000000000 1689031 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": 1202378, "vin": [ { "gen": { "height": 1202368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6874c67df169940c359b45dc749091e5d365a8a89956ea141c4d0d637aa48392" } } ], "extra": [ 1, 183, 72, 92, 189, 36, 205, 185, 130, 162, 177, 240, 174, 169, 86, 218, 162, 23, 104, 168, 62, 179, 133, 250, 43, 50, 14, 127, 106, 212, 36, 22, 4, 2, 17, 0, 0, 0, 9, 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