Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2c1c05c7d40f59cf8b3df42aa9ff64b001fa856099af620dbb41aa11c55952f

Tx prefix hash: 6b8ffd180929580a551c678c3b861e97f8fe3c25033bb63c71ef5caf64f128b0
Tx public key: 8b40f323d14f5bcbe9deddaa2176521438fff6511fd315d070e44eeff7be2775
Timestamp: 1784315731 Timestamp [UTC]: 2026-07-17 19:15:31 Age [y:d:h:m:s]: 00:125:04:26:24
Block: 1583958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 98282 RingCT/type: yes/0
Extra: 018b40f323d14f5bcbe9deddaa2176521438fff6511fd315d070e44eeff7be2775020855089b3fae2f27e7

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 35a38d02faf1a2eede2f416c7489c5fd58cbf9b9579b1c4888d72361d13e82a1 0.000600000000 2073952 of 15 <69>

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": 1583968, "vin": [ { "gen": { "height": 1583958 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "35a38d02faf1a2eede2f416c7489c5fd58cbf9b9579b1c4888d72361d13e82a1", "view_tag": "69" } } } ], "extra": [ 1, 139, 64, 243, 35, 209, 79, 91, 203, 233, 222, 221, 170, 33, 118, 82, 20, 56, 255, 246, 81, 31, 211, 21, 208, 112, 228, 78, 239, 247, 190, 39, 117, 2, 8, 85, 8, 155, 63, 174, 47, 39, 231 ], "rct_signatures": { "type": 0 } }


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