Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51d2594c9fc6fb2bca03e3792f4803dc1fede46cf9345b67f71f9c8d670a1b08

Tx prefix hash: b85c6d2b059b0466776a5ce98750754e88ee70fd879df353b5bb39b78a9a6632
Tx public key: 0573bd545484ad006f734ca63358ee3983f70b8f4361fa957de5f2783e7746e1
Timestamp: 1787394946 Timestamp [UTC]: 2026-08-22 10:35:46 Age [y:d:h:m:s]: 00:087:18:08:37
Block: 1618859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 62032 RingCT/type: yes/0
Extra: 010573bd545484ad006f734ca63358ee3983f70b8f4361fa957de5f2783e7746e10208e9240749e2d0832d

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 31f538d38762e9b1c4596f6cca9526a4bbb20f990909bbbb6332d43c0e17d78a 0.000600000000 2108879 of 15 <0c>

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": 1618869, "vin": [ { "gen": { "height": 1618859 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "31f538d38762e9b1c4596f6cca9526a4bbb20f990909bbbb6332d43c0e17d78a", "view_tag": "0c" } } } ], "extra": [ 1, 5, 115, 189, 84, 84, 132, 173, 0, 111, 115, 76, 166, 51, 88, 238, 57, 131, 247, 11, 143, 67, 97, 250, 149, 125, 229, 242, 120, 62, 119, 70, 225, 2, 8, 233, 36, 7, 73, 226, 208, 131, 45 ], "rct_signatures": { "type": 0 } }


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