Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b53809a1eb2dd7bc1e99ca16cc81a6f7d7dcf30bcf5046da668fb0a2da86081

Tx prefix hash: 8e7147a245e45b711ee9124768105452b208ba752279f0d6d9f502a113b91105
Tx public key: 0af0421730cf50237f2bca80a513a81ff365e03c2aef6853af6189699670f0cf
Timestamp: 1772624216 Timestamp [UTC]: 2026-03-04 11:36:56 Age [y:d:h:m:s]: 00:258:09:39:25
Block: 1490477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190173 RingCT/type: yes/0
Extra: 010af0421730cf50237f2bca80a513a81ff365e03c2aef6853af6189699670f0cf021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5717f38d8271dcc0fedc7af287630764955a024ada9a09a98bbd2bba3ad86f1b 0.000600000000 1979981 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": 1490487, "vin": [ { "gen": { "height": 1490477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5717f38d8271dcc0fedc7af287630764955a024ada9a09a98bbd2bba3ad86f1b" } } ], "extra": [ 1, 10, 240, 66, 23, 48, 207, 80, 35, 127, 43, 202, 128, 165, 19, 168, 31, 243, 101, 224, 60, 42, 239, 104, 83, 175, 97, 137, 105, 150, 112, 240, 207, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: