Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ef3d1e64f359c383ccbc2b1f77f021c689b68d6c6e16df04d0bb27c9c54956a

Tx prefix hash: 678aaf2c51977f0bdb071e0a101676ae45ad5fd1c1bd011aa99c0690891a0e1a
Tx public key: fd72f8ea8fa5c8098e0c0a17299d7dc85a64d085aaa56e0c14f4b342eb832257
Timestamp: 1785097385 Timestamp [UTC]: 2026-07-26 20:23:05 Age [y:d:h:m:s]: 00:118:08:15:36
Block: 1596410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 87084 RingCT/type: yes/0
Extra: 01fd72f8ea8fa5c8098e0c0a17299d7dc85a64d085aaa56e0c14f4b342eb832257

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2f6aac7b38946eb6b75e80b39c7d39c58dd9e4ccab661fdc9204c799eb9c7a7a 0.000600000000 2086428 of 15 <99>

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": 1596420, "vin": [ { "gen": { "height": 1596410 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "2f6aac7b38946eb6b75e80b39c7d39c58dd9e4ccab661fdc9204c799eb9c7a7a", "view_tag": "99" } } } ], "extra": [ 1, 253, 114, 248, 234, 143, 165, 200, 9, 142, 12, 10, 23, 41, 157, 125, 200, 90, 100, 208, 133, 170, 165, 110, 12, 20, 244, 179, 66, 235, 131, 34, 87 ], "rct_signatures": { "type": 0 } }


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