Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c549cbbd47095084a56d72bc0eacec13c942d4b1bf58db8abb939da0e87a8da4

Tx prefix hash: 67d7adf4870d6fa9efb1ab6c39638c24936d52af9dc1d7fd1d4499328316a03e
Tx public key: 82fd8ea19fadb3e2e9fb3036bbef4d4a84fe17b5e708660369e5a9a6aa6b2b87
Timestamp: 1736266284 Timestamp [UCT]: 2025-01-07 16:11:24 Age [y:d:h:m:s]: 00:093:10:54:45
Block: 1192275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66581 RingCT/type: yes/0
Extra: 0182fd8ea19fadb3e2e9fb3036bbef4d4a84fe17b5e708660369e5a9a6aa6b2b87021100000014007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dd0cc5ccdf289ff971069152d36463101fb82c5eb486c5dc036f7c8a20b98f4 0.600000000000 1678824 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": 1192285, "vin": [ { "gen": { "height": 1192275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dd0cc5ccdf289ff971069152d36463101fb82c5eb486c5dc036f7c8a20b98f4" } } ], "extra": [ 1, 130, 253, 142, 161, 159, 173, 179, 226, 233, 251, 48, 54, 187, 239, 77, 74, 132, 254, 23, 181, 231, 8, 102, 3, 105, 229, 169, 166, 170, 107, 43, 135, 2, 17, 0, 0, 0, 20, 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