Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1d5780c46df2ceb36825519af6efe38c4e954fdb147e92294df00968a647a86

Tx prefix hash: d109183ea55eef7e8df9af07831d7f5a2cc1de2e24fe69149b96b23b0dfd30ac
Tx public key: 1f5e963a2bf2cc06b302d4800a14e37b9dcc7fdec110d3f0a7b7fe264abf73ba
Timestamp: 1772689148 Timestamp [UTC]: 2026-03-05 05:39:08 Age [y:d:h:m:s]: 00:255:02:21:12
Block: 1491017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187738 RingCT/type: yes/0
Extra: 011f5e963a2bf2cc06b302d4800a14e37b9dcc7fdec110d3f0a7b7fe264abf73ba021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4c2078843df70d6d3f0989543c47ebd98e92bf0b948988ebf50e186e43a56887 0.000600000000 1980531 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": 1491027, "vin": [ { "gen": { "height": 1491017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c2078843df70d6d3f0989543c47ebd98e92bf0b948988ebf50e186e43a56887" } } ], "extra": [ 1, 31, 94, 150, 58, 43, 242, 204, 6, 179, 2, 212, 128, 10, 20, 227, 123, 157, 204, 127, 222, 193, 16, 211, 240, 167, 183, 254, 38, 74, 191, 115, 186, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: