Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b01980bb84fe8f394551a6317a0eb0a99cbe22d78b00a4fbb8580f20cd089b80

Tx prefix hash: bbd67d0f60be9e20e939add9d61f0a0a860d0b8844e6a03b9da0e81d293a99f3
Tx public key: 9cf2bd64fb2e4e43a2adba38fdf04996f622e41587b65c8ec2556d9cdc166233
Timestamp: 1785901334 Timestamp [UTC]: 2026-08-05 03:42:14 Age [y:d:h:m:s]: 00:101:19:49:18
Block: 1606219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 72267 RingCT/type: yes/0
Extra: 019cf2bd64fb2e4e43a2adba38fdf04996f622e41587b65c8ec2556d9cdc166233

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c745659fc31e97754502cf90fe30d6cde39f83c64cb6677d1b9d00269bd12030 0.000600000000 2096239 of 15 <f5>

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": 1606229, "vin": [ { "gen": { "height": 1606219 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "c745659fc31e97754502cf90fe30d6cde39f83c64cb6677d1b9d00269bd12030", "view_tag": "f5" } } } ], "extra": [ 1, 156, 242, 189, 100, 251, 46, 78, 67, 162, 173, 186, 56, 253, 240, 73, 150, 246, 34, 228, 21, 135, 182, 92, 142, 194, 85, 109, 156, 220, 22, 98, 51 ], "rct_signatures": { "type": 0 } }


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