Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d4ae95d5c137ad488e2a5c0082b7c161bf37a3ef02f6ac1a166796f45faf9f3

Tx prefix hash: 3b95c669c0263bde86b18d4197dcbedf2c8888a1ecff138e0d82d2ad5e2a366c
Tx public key: 2ba5e6fddc74b0feb37f0c6b46f80fc3d4e4dfff8bd13905e7b6433bbc1bb75e
Timestamp: 1753691139 Timestamp [UCT]: 2025-07-28 08:25:39 Age [y:d:h:m:s]: 00:068:14:32:06
Block: 1335095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47803 RingCT/type: yes/0
Extra: 012ba5e6fddc74b0feb37f0c6b46f80fc3d4e4dfff8bd13905e7b6433bbc1bb75e021100000006db6acbd3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cd2c8c4f103f56dfa7b905d067bc47a7df470adc0ff1774121178b32e20bc90 0.600000000000 1822896 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": 1335105, "vin": [ { "gen": { "height": 1335095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cd2c8c4f103f56dfa7b905d067bc47a7df470adc0ff1774121178b32e20bc90" } } ], "extra": [ 1, 43, 165, 230, 253, 220, 116, 176, 254, 179, 127, 12, 107, 70, 248, 15, 195, 212, 228, 223, 255, 139, 209, 57, 5, 231, 182, 67, 59, 188, 27, 183, 94, 2, 17, 0, 0, 0, 6, 219, 106, 203, 211, 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