Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a080712f61b282b2bf937b5f7eee0d5046e9ab2543c082d00731e9e11f88c11c

Tx prefix hash: 117bf05dc84c46f96bc4554faf5088ae8c0d2bfeddd2d53a7c45b61e9cb64b13
Tx public key: 86f299e62f091af8afe8fa3f1568a8ae3ddc05ce74b5f14d6ee40d6a58adb14b
Timestamp: 1780596679 Timestamp [UTC]: 2026-06-04 18:11:19 Age [y:d:h:m:s]: 00:170:08:25:48
Block: 1551252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 132242 RingCT/type: yes/0
Extra: 0186f299e62f091af8afe8fa3f1568a8ae3ddc05ce74b5f14d6ee40d6a58adb14b

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b59b12f7c306c343adaba0fb24cc351a418df07a12a1cfc8d52c4b1b3879b7ee 0.000600000000 2041226 of 15 <42>

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": 1551262, "vin": [ { "gen": { "height": 1551252 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "b59b12f7c306c343adaba0fb24cc351a418df07a12a1cfc8d52c4b1b3879b7ee", "view_tag": "42" } } } ], "extra": [ 1, 134, 242, 153, 230, 47, 9, 26, 248, 175, 232, 250, 63, 21, 104, 168, 174, 61, 220, 5, 206, 116, 181, 241, 77, 110, 228, 13, 106, 88, 173, 177, 75 ], "rct_signatures": { "type": 0 } }


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