Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebb58e75d44ce21d045fd2f005c3f7d44a05d6671fde4bc7eaf5027762c65d14

Tx prefix hash: ec3daa96523256535bd5d66c5845c0c67498121792684682d46a17ecffa333c1
Tx public key: 4c0e1f4ccc73cdac76a492aba6cda7aa9d31a4cb1a0e28ebc6aa8c6983598826
Timestamp: 1735299144 Timestamp [UCT]: 2024-12-27 11:32:24 Age [y:d:h:m:s]: 00:096:22:09:06
Block: 1184265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69056 RingCT/type: yes/0
Extra: 014c0e1f4ccc73cdac76a492aba6cda7aa9d31a4cb1a0e28ebc6aa8c6983598826021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f68eeeb98ea3dcf3cd087bb9415e256838794ac87f901a3742d720a63d5db071 0.600000000000 1670722 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": 1184275, "vin": [ { "gen": { "height": 1184265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f68eeeb98ea3dcf3cd087bb9415e256838794ac87f901a3742d720a63d5db071" } } ], "extra": [ 1, 76, 14, 31, 76, 204, 115, 205, 172, 118, 164, 146, 171, 166, 205, 167, 170, 157, 49, 164, 203, 26, 14, 40, 235, 198, 170, 140, 105, 131, 89, 136, 38, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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