Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d2b1fdf7d3cffc4abfb1cc5dd2ac161f1a7649c7d93be41b4da50f883eb30cf

Tx prefix hash: 654b39ed74a6d9f400d78c1e82ae08d99ad57f7a60f0d36954b2fb1b51b0cb38
Tx public key: 38bc5af0b164838269444c41b045a2be00383b1f5ff0070b225a2a7652210feb
Timestamp: 1785442697 Timestamp [UTC]: 2026-07-30 20:18:17 Age [y:d:h:m:s]: 00:111:23:29:06
Block: 1602291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 79823 RingCT/type: yes/0
Extra: 0138bc5af0b164838269444c41b045a2be00383b1f5ff0070b225a2a7652210feb0208d8280011f6a50268

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: acecac185a4894125f2fcc856249ee0b7668d100471d9c84f5f7d4dc6dc1c536 0.000600000000 2092309 of 15 <ec>

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": 1602301, "vin": [ { "gen": { "height": 1602291 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "acecac185a4894125f2fcc856249ee0b7668d100471d9c84f5f7d4dc6dc1c536", "view_tag": "ec" } } } ], "extra": [ 1, 56, 188, 90, 240, 177, 100, 131, 130, 105, 68, 76, 65, 176, 69, 162, 190, 0, 56, 59, 31, 95, 240, 7, 11, 34, 90, 42, 118, 82, 33, 15, 235, 2, 8, 216, 40, 0, 17, 246, 165, 2, 104 ], "rct_signatures": { "type": 0 } }


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