Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b998f5cf889d5e9248eff839fcdd6dffd24b32c0c98ef76e53f4c5231f29d65d

Tx prefix hash: 79e0f2817887a01dfdbfedde4aed524e51d6460841854f782164ffbe36c8a10e
Tx public key: 811b3a7eb3ef3953dd205759cd35a4d7309f6d5335d2f54602eb07040fb9e968
Timestamp: 1705952950 Timestamp [UCT]: 2024-01-22 19:49:10 Age [y:d:h:m:s]: 01:083:17:06:02
Block: 941062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320939 RingCT/type: yes/0
Extra: 01811b3a7eb3ef3953dd205759cd35a4d7309f6d5335d2f54602eb07040fb9e9680211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d768732a74b2027fd50a634d6c5568a97800857e09d212e2b172ef6a5ba686c7 0.600000000000 1399204 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": 941072, "vin": [ { "gen": { "height": 941062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d768732a74b2027fd50a634d6c5568a97800857e09d212e2b172ef6a5ba686c7" } } ], "extra": [ 1, 129, 27, 58, 126, 179, 239, 57, 83, 221, 32, 87, 89, 205, 53, 164, 215, 48, 159, 109, 83, 53, 210, 245, 70, 2, 235, 7, 4, 15, 185, 233, 104, 2, 17, 0, 0, 0, 7, 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