Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2d6e5c431b9b6a2fe65eab94f3ce2e65a717a141ec9a767f69cd9dfd9962932

Tx prefix hash: bd39c098b8f2d4f636a223e0790b6d38853ec62cfd830df2401a5d0ac77aa835
Tx public key: ddc2a1c904e9b899c0872042e088663f156d91f6f3ea1015346e9199e8f2d303
Timestamp: 1758734223 Timestamp [UTC]: 2025-09-24 17:17:03 Age [y:d:h:m:s]: 01:052:23:53:10
Block: 1375569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304216 RingCT/type: yes/0
Extra: 01ddc2a1c904e9b899c0872042e088663f156d91f6f3ea1015346e9199e8f2d303021100000007b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 257004de9b6a133befeaed59c7480129a672255d6a750e6289ce9e41cd0cca58 0.000600000000 1863660 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 dinastycoin-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": 1375579, "vin": [ { "gen": { "height": 1375569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "257004de9b6a133befeaed59c7480129a672255d6a750e6289ce9e41cd0cca58" } } ], "extra": [ 1, 221, 194, 161, 201, 4, 233, 184, 153, 192, 135, 32, 66, 224, 136, 102, 63, 21, 109, 145, 246, 243, 234, 16, 21, 52, 110, 145, 153, 232, 242, 211, 3, 2, 17, 0, 0, 0, 7, 178, 247, 132, 196, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: