Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a21c5c26c608b7031b6ab1211689656dcd3f5c9d5c90fe09f0d098b3fae5274f

Tx prefix hash: 72548cad18cb19c295ca25d876746de6420d03074c3e398d6bd5218e6607daff
Tx public key: 88529985355d10a97d46385e7392156b618e0ba4ae5cfc9ac3721091a183a674
Timestamp: 1774074416 Timestamp [UTC]: 2026-03-21 06:26:56 Age [y:d:h:m:s]: 00:239:14:47:27
Block: 1502452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176715 RingCT/type: yes/0
Extra: 0188529985355d10a97d46385e7392156b618e0ba4ae5cfc9ac3721091a183a67402110000000cf188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fcae41a66cbc607c725c4e86944bfe7e3a4a73ee362a1ff77f4c9b9883c1f484 0.000600000000 1992150 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": 1502462, "vin": [ { "gen": { "height": 1502452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcae41a66cbc607c725c4e86944bfe7e3a4a73ee362a1ff77f4c9b9883c1f484" } } ], "extra": [ 1, 136, 82, 153, 133, 53, 93, 16, 169, 125, 70, 56, 94, 115, 146, 21, 107, 97, 142, 11, 164, 174, 92, 252, 154, 195, 114, 16, 145, 161, 131, 166, 116, 2, 17, 0, 0, 0, 12, 241, 136, 200, 168, 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: