Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2657007e95a5e660b9cd0a48b6b1ebc9380309fc9aa3f0a984d611aa4e8fefdc

Tx prefix hash: c6f1e80f652cd2303032c12fe25d4a4a83e1db1eb916798496a2a43abda3426d
Tx public key: eb9c3f6a969697ce21b443cb5fdd2fce4bad013f1c7966e001bc6a071fa43ae6
Timestamp: 1751318693 Timestamp [UCT]: 2025-06-30 21:24:53 Age [y:d:h:m:s]: 00:143:06:36:49
Block: 1316114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100576 RingCT/type: yes/0
Extra: 01eb9c3f6a969697ce21b443cb5fdd2fce4bad013f1c7966e001bc6a071fa43ae602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 688194491bce41fb5e0bd55cba78c0af77b0f1096957f6f1f272c7feb9fc2a73 0.600000000000 1803771 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": 1316124, "vin": [ { "gen": { "height": 1316114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "688194491bce41fb5e0bd55cba78c0af77b0f1096957f6f1f272c7feb9fc2a73" } } ], "extra": [ 1, 235, 156, 63, 106, 150, 150, 151, 206, 33, 180, 67, 203, 95, 221, 47, 206, 75, 173, 1, 63, 28, 121, 102, 224, 1, 188, 106, 7, 31, 164, 58, 230, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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