Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9e82ecf08cf9077719aeaf9e2b3ba9201c4c39d23a9527162c862e9916f0406

Tx prefix hash: b5957e35fb79ddd96f3fda4e3437fae5e89729ae1f7c89dab5d9fde6b0c48208
Tx public key: 498ca80fd46f9e93139738a4c1cf5519cd6a2e3f9ad6fbcd705f2e8a8e7e6da4
Timestamp: 1711359782 Timestamp [UCT]: 2024-03-25 09:43:02 Age [y:d:h:m:s]: 01:050:04:31:57
Block: 985951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296849 RingCT/type: yes/0
Extra: 01498ca80fd46f9e93139738a4c1cf5519cd6a2e3f9ad6fbcd705f2e8a8e7e6da40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c666f863ac11e703a38ed2883ab35b957789409d5d811184bb74cfd03e99181 0.600000000000 1446172 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": 985961, "vin": [ { "gen": { "height": 985951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c666f863ac11e703a38ed2883ab35b957789409d5d811184bb74cfd03e99181" } } ], "extra": [ 1, 73, 140, 168, 15, 212, 111, 158, 147, 19, 151, 56, 164, 193, 207, 85, 25, 205, 106, 46, 63, 154, 214, 251, 205, 112, 95, 46, 138, 142, 126, 109, 164, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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