Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95a94ca5bc51c8eb85666bb32c990e0879a5776c12586cd133b72a680bd9ef1a

Tx prefix hash: e4c41a86b0197a236a5b7fb9bd0a4ce189a8ba95bccccefc06e475e7922c721d
Tx public key: ba8dc2646aa17dffcef57b056faa702a97b1f777dac6dac9f81d1250610e6181
Timestamp: 1747729036 Timestamp [UTC]: 2025-05-20 08:17:16 Age [y:d:h:m:s]: 01:183:18:51:50
Block: 1286906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395449 RingCT/type: yes/0
Extra: 01ba8dc2646aa17dffcef57b056faa702a97b1f777dac6dac9f81d1250610e61810211000000029f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bb545329a2701967d99ba2c4492f07156429113effe11bda608887e79d64f8ee 0.000600000000 1774373 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": 1286916, "vin": [ { "gen": { "height": 1286906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb545329a2701967d99ba2c4492f07156429113effe11bda608887e79d64f8ee" } } ], "extra": [ 1, 186, 141, 194, 100, 106, 161, 125, 255, 206, 245, 123, 5, 111, 170, 112, 42, 151, 177, 247, 119, 218, 198, 218, 201, 248, 29, 18, 80, 97, 14, 97, 129, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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: