Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ac52d27134ec7df3f2d53b28608ea83d9e39c0478f34ebef89372a85dac4415

Tx prefix hash: e136d27b74b3e2d170b14c8ecbc71d26c3ca8a39d20c37b20a4ed2582350c638
Tx public key: c1223e398c63508d4f48c0a9498e003bc10e94b8dd0f729be21e753bc9de44f0
Timestamp: 1728038526 Timestamp [UCT]: 2024-10-04 10:42:06 Age [y:d:h:m:s]: 00:051:07:45:10
Block: 1124205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36655 RingCT/type: yes/0
Extra: 01c1223e398c63508d4f48c0a9498e003bc10e94b8dd0f729be21e753bc9de44f0021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2c03be0bd26ccc59dcbb6b1028c60daaa3c91114b27394924cbe951ebd2d7e7 0.600000000000 1606796 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": 1124215, "vin": [ { "gen": { "height": 1124205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2c03be0bd26ccc59dcbb6b1028c60daaa3c91114b27394924cbe951ebd2d7e7" } } ], "extra": [ 1, 193, 34, 62, 57, 140, 99, 80, 141, 79, 72, 192, 169, 73, 142, 0, 59, 193, 14, 148, 184, 221, 15, 114, 155, 226, 30, 117, 59, 201, 222, 68, 240, 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