Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b278d01792b9b3b4f633f3cbb5e868fa4080e14f1350daf078a245b6132671fb

Tx prefix hash: de74852ea9e6d75dec715f79900007f2329eafede0cd99d84d5111ed3c295436
Tx public key: d3545a9607c4769f42faa3a02ca2fbe4159868d2bb46784a0e5a4a91f8962100
Timestamp: 1783210166 Timestamp [UTC]: 2026-07-05 00:09:26 Age [y:d:h:m:s]: 00:139:15:04:56
Block: 1574835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 108654 RingCT/type: yes/0
Extra: 01d3545a9607c4769f42faa3a02ca2fbe4159868d2bb46784a0e5a4a91f896210002085eaf9bcc6a775825

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d9ca34b1cf3f46e80d128b865bae788461cb0a79f4e898f75dc64f98bb22be99 0.000600000000 2064817 of 15 <52>

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": 1574845, "vin": [ { "gen": { "height": 1574835 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "d9ca34b1cf3f46e80d128b865bae788461cb0a79f4e898f75dc64f98bb22be99", "view_tag": "52" } } } ], "extra": [ 1, 211, 84, 90, 150, 7, 196, 118, 159, 66, 250, 163, 160, 44, 162, 251, 228, 21, 152, 104, 210, 187, 70, 120, 74, 14, 90, 74, 145, 248, 150, 33, 0, 2, 8, 94, 175, 155, 204, 106, 119, 88, 37 ], "rct_signatures": { "type": 0 } }


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