Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 697edc6258103e5cbf500d8bf68a3d6d8c41ee78f35a6f6b4d6cd13654880c3e

Tx prefix hash: bdcabaddb03261bea41730c2ea5484f3ee9fe484850b1b2ae2a61413323a35f1
Tx public key: c249946942c3424e4a7aa44141bdb9f1debaea431d926df6f973c095801678e3
Timestamp: 1775138553 Timestamp [UTC]: 2026-04-02 14:02:33 Age [y:d:h:m:s]: 00:230:18:36:45
Block: 1511263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170498 RingCT/type: yes/0
Extra: 01c249946942c3424e4a7aa44141bdb9f1debaea431d926df6f973c095801678e3021100000002e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f3f5dfc3ee27c2f2a656ab3abfddc1bd8102579f792640fc4bba7e0a48859dce 0.000600000000 2001053 of 15 -

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": 1511273, "vin": [ { "gen": { "height": 1511263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3f5dfc3ee27c2f2a656ab3abfddc1bd8102579f792640fc4bba7e0a48859dce" } } ], "extra": [ 1, 194, 73, 148, 105, 66, 195, 66, 78, 74, 122, 164, 65, 65, 189, 185, 241, 222, 186, 234, 67, 29, 146, 109, 246, 249, 115, 192, 149, 128, 22, 120, 227, 2, 17, 0, 0, 0, 2, 227, 215, 220, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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