Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91ac30ab555e249fa825d8a1d6a3b5a7f93672f2202c554921bfa5a2cfa84717

Tx prefix hash: afd9be6c9e7993a53143e244ae002256151fa558b722137c1a2733ec24105888
Tx public key: 872a56023a030209b2113f25a4df071df2dbb617034e23a2c73e86bdb225c92d
Timestamp: 1738333954 Timestamp [UCT]: 2025-01-31 14:32:34 Age [y:d:h:m:s]: 00:293:22:46:08
Block: 1209130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207835 RingCT/type: yes/0
Extra: 01872a56023a030209b2113f25a4df071df2dbb617034e23a2c73e86bdb225c92d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74df5552f005887b80b8bb8d85d0057dbca6ca1e2efd27d4b4cbde5c3b931a37 0.600000000000 1695871 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": 1209140, "vin": [ { "gen": { "height": 1209130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74df5552f005887b80b8bb8d85d0057dbca6ca1e2efd27d4b4cbde5c3b931a37" } } ], "extra": [ 1, 135, 42, 86, 2, 58, 3, 2, 9, 178, 17, 63, 37, 164, 223, 7, 29, 242, 219, 182, 23, 3, 78, 35, 162, 199, 62, 134, 189, 178, 37, 201, 45, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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