Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 561349ad96fc91e6df3171f1b7cbcc9ae57611f73aa115a574c34a57dc1fe50b

Tx prefix hash: adc0e8a11ad5a369d4cde2d3dbc2fafdabbfe9f2b2f3064fe073da367d1b4442
Tx public key: 9a7a3cd8ddf9e19e4d9919fc6c06ec9ae488e9cddbc1747ed3361cdfa09b3ad8
Timestamp: 1764672011 Timestamp [UCT]: 2025-12-02 10:40:11 Age [y:d:h:m:s]: 00:003:11:48:06
Block: 1424785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2487 RingCT/type: yes/0
Extra: 019a7a3cd8ddf9e19e4d9919fc6c06ec9ae488e9cddbc1747ed3361cdfa09b3ad8021100000005da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0460126bc3c6f2a16bbcff24c456c37b0adb128c6b190db14ef63e1b97f91568 0.600000000000 1913416 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": 1424795, "vin": [ { "gen": { "height": 1424785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0460126bc3c6f2a16bbcff24c456c37b0adb128c6b190db14ef63e1b97f91568" } } ], "extra": [ 1, 154, 122, 60, 216, 221, 249, 225, 158, 77, 153, 25, 252, 108, 6, 236, 154, 228, 136, 233, 205, 219, 193, 116, 126, 211, 54, 28, 223, 160, 155, 58, 216, 2, 17, 0, 0, 0, 5, 218, 85, 72, 72, 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