Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66ac7d56fe6fd27b0f0822db06a330733a7a4ed3cf8024b755280f13c2483583

Tx prefix hash: f4cb4c78cefd1216612367ddac1889371e2eed311ec8c9bed1e0a47159bd1eac
Tx public key: d4df3d692c3ccca0da07200aac9d335fdae9760dfe3af228e4ed9e139bbe9a50
Timestamp: 1740763080 Timestamp [UCT]: 2025-02-28 17:18:00 Age [y:d:h:m:s]: 00:337:03:14:46
Block: 1229226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238625 RingCT/type: yes/0
Extra: 01d4df3d692c3ccca0da07200aac9d335fdae9760dfe3af228e4ed9e139bbe9a500211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d986647370da4f3ab747df347711b678dd91a065d5a68b818d04dd88fd2feda 0.600000000000 1716111 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": 1229236, "vin": [ { "gen": { "height": 1229226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d986647370da4f3ab747df347711b678dd91a065d5a68b818d04dd88fd2feda" } } ], "extra": [ 1, 212, 223, 61, 105, 44, 60, 204, 160, 218, 7, 32, 10, 172, 157, 51, 95, 218, 233, 118, 13, 254, 58, 242, 40, 228, 237, 158, 19, 155, 190, 154, 80, 2, 17, 0, 0, 0, 2, 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