Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8b87d784ac375c8f1ea5edc63513bef472dd10c6c34fad9e8c3fddc68775bcf

Tx prefix hash: e7f5b1c93233dd768e3ec69d5871eff504a654baddd32ae73be7fd2654414332
Tx public key: f193f833b50cd6cd03f58f309e468f906a87b768653ce1faac1106aca655a7a8
Timestamp: 1734967277 Timestamp [UCT]: 2024-12-23 15:21:17 Age [y:d:h:m:s]: 00:104:01:54:45
Block: 1181551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74135 RingCT/type: yes/0
Extra: 01f193f833b50cd6cd03f58f309e468f906a87b768653ce1faac1106aca655a7a80211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ed66861ce1c6b073e342dd31e5d78d1ba1ad4cee8c3a46ced4a4f16e4a0d1a4 0.600000000000 1667976 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": 1181561, "vin": [ { "gen": { "height": 1181551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ed66861ce1c6b073e342dd31e5d78d1ba1ad4cee8c3a46ced4a4f16e4a0d1a4" } } ], "extra": [ 1, 241, 147, 248, 51, 181, 12, 214, 205, 3, 245, 143, 48, 158, 70, 143, 144, 106, 135, 183, 104, 101, 60, 225, 250, 172, 17, 6, 172, 166, 85, 167, 168, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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