Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c97dbd84643b868522029d92f5e077091450a68d25f7fe047c6ca85dce73124

Tx prefix hash: c93351e0b331676dd7f1f8b36137d857c18d388bf7c74674ccb13170cd5b3c67
Tx public key: 51dbd2eebe4ba9387f5c4a7e52b6db3c933934e5d70eafdbe7c6950de1709429
Timestamp: 1714076219 Timestamp [UTC]: 2024-04-25 20:16:59 Age [y:d:h:m:s]: 02:207:19:21:23
Block: 1008437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 673546 RingCT/type: yes/0
Extra: 0151dbd2eebe4ba9387f5c4a7e52b6db3c933934e5d70eafdbe7c6950de170942902110000000159dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 63a81a52dcb3c273189eaa1f5e6f0513ef62f4d8b907061426aaa5b1b08a7eff 0.000600000000 1469907 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": 1008447, "vin": [ { "gen": { "height": 1008437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63a81a52dcb3c273189eaa1f5e6f0513ef62f4d8b907061426aaa5b1b08a7eff" } } ], "extra": [ 1, 81, 219, 210, 238, 190, 75, 169, 56, 127, 92, 74, 126, 82, 182, 219, 60, 147, 57, 52, 229, 215, 14, 175, 219, 231, 198, 149, 13, 225, 112, 148, 41, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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: