Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e22063ecbf2465c1bb21b0de5dd4c9121c95124d9faf58aa4d3a9aa7679de7ed

Tx prefix hash: 64e607a3d0dfe2f466ff0eb268640c5ff17887554a15d45b4cd6298b34bc87e1
Tx public key: 0ca4c81ab9ddf7ee86d964e1ab028a1e88be2a881a0702bcbdc733925ae2d0d3
Timestamp: 1584420979 Timestamp [UCT]: 2020-03-17 04:56:19 Age [y:d:h:m:s]: 04:305:02:08:51
Block: 83833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113886 RingCT/type: yes/0
Extra: 010ca4c81ab9ddf7ee86d964e1ab028a1e88be2a881a0702bcbdc733925ae2d0d302110000000cd81c26c0000000000000000000

1 output(s) for total of 323.763029079000 dcy

stealth address amount amount idx
00: e2a398c221caf7d0c438064e84c3e2da283372c4ac6cb192ded934607c9bbe6a 323.763029079000 152327 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": 83843, "vin": [ { "gen": { "height": 83833 } } ], "vout": [ { "amount": 323763029079, "target": { "key": "e2a398c221caf7d0c438064e84c3e2da283372c4ac6cb192ded934607c9bbe6a" } } ], "extra": [ 1, 12, 164, 200, 26, 185, 221, 247, 238, 134, 217, 100, 225, 171, 2, 138, 30, 136, 190, 42, 136, 26, 7, 2, 188, 189, 199, 51, 146, 90, 226, 208, 211, 2, 17, 0, 0, 0, 12, 216, 28, 38, 192, 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