Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c1138afc0d8ef39d628c7122beb0d4b72fb6ec2b7796f6c418f625dd2862a32

Tx prefix hash: 3879f16bdd427e3917c43c964ff66e19c5ccfc02e5d7b1899c2b8f8ef2f8905d
Tx public key: cb4afeed7967b5c5dc4b28e38c27c30a6faf523f911be85328f394cca3b79112
Timestamp: 1746297917 Timestamp [UTC]: 2025-05-03 18:45:17 Age [y:d:h:m:s]: 01:201:00:27:25
Block: 1275054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407830 RingCT/type: yes/0
Extra: 01cb4afeed7967b5c5dc4b28e38c27c30a6faf523f911be85328f394cca3b79112021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a6c8401c75bac7d08bdd1401db8edace4d96fb8c15afef05e1b4d725e4c9339f 0.000600000000 1762359 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": 1275064, "vin": [ { "gen": { "height": 1275054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6c8401c75bac7d08bdd1401db8edace4d96fb8c15afef05e1b4d725e4c9339f" } } ], "extra": [ 1, 203, 74, 254, 237, 121, 103, 181, 197, 220, 75, 40, 227, 140, 39, 195, 10, 111, 175, 82, 63, 145, 27, 232, 83, 40, 243, 148, 204, 163, 183, 145, 18, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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: