Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b012fef072f4d9b2f824f4ebbf4fe6bd0ee12a19c25cfc4eee5d122915bedb3e

Tx prefix hash: da7f46e703beacee597ede2874c1a6c445c61b6dbc2203c2f76bb0352e0c8cfd
Tx public key: 0727414f06e85974d8f85b58856baf2cb799f9a5f7cee0a2dac79752176b91e1
Timestamp: 1794002518 Timestamp [UTC]: 2026-11-06 22:01:58 Age [y:d:h:m:s]: 00:001:15:21:25
Block: 1672113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 1334 RingCT/type: yes/0
Extra: 010727414f06e85974d8f85b58856baf2cb799f9a5f7cee0a2dac79752176b91e1

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4b5f0d102abc2b11dc4f6e37dba36a9ba95e45b4a94c6608276931b8919a9fa1 0.000600000000 2162875 of 15 <4c>

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": 1672123, "vin": [ { "gen": { "height": 1672113 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "4b5f0d102abc2b11dc4f6e37dba36a9ba95e45b4a94c6608276931b8919a9fa1", "view_tag": "4c" } } } ], "extra": [ 1, 7, 39, 65, 79, 6, 232, 89, 116, 216, 248, 91, 88, 133, 107, 175, 44, 183, 153, 249, 165, 247, 206, 224, 162, 218, 199, 151, 82, 23, 107, 145, 225 ], "rct_signatures": { "type": 0 } }


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