Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b17da1267fd404dc25c93c2d037b06af9bad99a7843904312e3b1caa024fe0

Tx prefix hash: 49a03b285df6255b0771b9b603524c4deb049855b0d37ac10412605222b22a5e
Tx public key: 65d15ca819623fcf0fe8d6f7c5edda2c557f6a4516026ee16b2a4ce94d15259e
Timestamp: 1742864246 Timestamp [UTC]: 2025-03-25 00:57:26 Age [y:d:h:m:s]: 01:241:11:11:57
Block: 1246625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436769 RingCT/type: yes/0
Extra: 0165d15ca819623fcf0fe8d6f7c5edda2c557f6a4516026ee16b2a4ce94d15259e02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf18aded92589108c7089796b01540d5f99a5dbefb1d2e4389034099e2177cd7 0.000600000000 1733626 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": 1246635, "vin": [ { "gen": { "height": 1246625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf18aded92589108c7089796b01540d5f99a5dbefb1d2e4389034099e2177cd7" } } ], "extra": [ 1, 101, 209, 92, 168, 25, 98, 63, 207, 15, 232, 214, 247, 197, 237, 218, 44, 85, 127, 106, 69, 22, 2, 110, 225, 107, 42, 76, 233, 77, 21, 37, 158, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: