Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09bdb2eb1c7e069dadc10db1cc8778be0b3c1bf254726ecc27efea0a26ce7083

Tx prefix hash: 944b63035861e64840c5295cbfd5fbd19680a8e9438fed15797f2815f6a3e51e
Tx public key: cc9697eb8fa2dd0f03c78b6e9e56e85c150ed5e18d678f202add300bb1198228
Timestamp: 1651614317 Timestamp [UCT]: 2022-05-03 21:45:17 Age [y:d:h:m:s]: 02:316:01:45:32
Block: 493751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745696 RingCT/type: yes/0
Extra: 01cc9697eb8fa2dd0f03c78b6e9e56e85c150ed5e18d678f202add300bb119822802110000000f2e6b1fd5000000000000000000

1 output(s) for total of 14.190515941000 dcy

stealth address amount amount idx
00: ef6c66106509c9d5d783746e3e25a9a293f3b885c8255dc22f70bf640d3fae65 14.190515941000 917304 of 0

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": 493761, "vin": [ { "gen": { "height": 493751 } } ], "vout": [ { "amount": 14190515941, "target": { "key": "ef6c66106509c9d5d783746e3e25a9a293f3b885c8255dc22f70bf640d3fae65" } } ], "extra": [ 1, 204, 150, 151, 235, 143, 162, 221, 15, 3, 199, 139, 110, 158, 86, 232, 92, 21, 14, 213, 225, 141, 103, 143, 32, 42, 221, 48, 11, 177, 25, 130, 40, 2, 17, 0, 0, 0, 15, 46, 107, 31, 213, 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