Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24a9f06cef51581f7e640b79995c0d1b119ac1ce53edb28c5d95e274e319d322

Tx prefix hash: a7c50ed939747bcd85f2e65beec39ce6092e35bb274eb09c6dea5b934af83e0d
Tx public key: e5d0003d5232dacaeffcf5fe351f9f85e41e92959a3f2b1747c30de822cacecf
Timestamp: 1728666897 Timestamp [UCT]: 2024-10-11 17:14:57 Age [y:d:h:m:s]: 00:180:10:17:07
Block: 1129410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128740 RingCT/type: yes/0
Extra: 01e5d0003d5232dacaeffcf5fe351f9f85e41e92959a3f2b1747c30de822cacecf021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8772c74f06a5951d1fe935bb865298af21fbe23682a5e288e6e1f49d6a1047e0 0.600000000000 1612237 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": 1129420, "vin": [ { "gen": { "height": 1129410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8772c74f06a5951d1fe935bb865298af21fbe23682a5e288e6e1f49d6a1047e0" } } ], "extra": [ 1, 229, 208, 0, 61, 82, 50, 218, 202, 239, 252, 245, 254, 53, 31, 159, 133, 228, 30, 146, 149, 154, 63, 43, 23, 71, 195, 13, 232, 34, 202, 206, 207, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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