Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: add533b46d35f4df7f229629386dd1f112afbc1503267b2c61d55f382f871217

Tx prefix hash: 781732af24696eeaff4c551b89479e73e9bfe99d32fc2342fb3837d4e5bbf128
Tx public key: f6c97a8847f59c52903eb78591d8b096eec609973596ed1dc0dd5c0a8bc786aa
Timestamp: 1713428377 Timestamp [UCT]: 2024-04-18 08:19:37 Age [y:d:h:m:s]: 01:026:04:22:53
Block: 1003055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279700 RingCT/type: yes/0
Extra: 01f6c97a8847f59c52903eb78591d8b096eec609973596ed1dc0dd5c0a8bc786aa0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fd5617eae5dfad3fee8167f95f9e6fa1dea13440595c73886983615c9d91f25 0.600000000000 1463585 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": 1003065, "vin": [ { "gen": { "height": 1003055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fd5617eae5dfad3fee8167f95f9e6fa1dea13440595c73886983615c9d91f25" } } ], "extra": [ 1, 246, 201, 122, 136, 71, 245, 156, 82, 144, 62, 183, 133, 145, 216, 176, 150, 238, 198, 9, 151, 53, 150, 237, 29, 192, 221, 92, 10, 139, 199, 134, 170, 2, 17, 0, 0, 0, 3, 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