Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a39db5b310b46c8283baddc2d701d91c63ffb94692afc0a4da37d65b20366f1

Tx prefix hash: fc8dbfba299b2dc35b5dc77eb2d086996248920a152fb232f61cdca5a8c59a8c
Tx public key: 9129f81d17ced9df37f3d94505feda0cd09996f34eda7f1ccd277ca013f04b23
Timestamp: 1705662521 Timestamp [UTC]: 2024-01-19 11:08:41 Age [y:d:h:m:s]: 02:306:05:57:14
Block: 938659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 744186 RingCT/type: yes/0
Extra: 019129f81d17ced9df37f3d94505feda0cd09996f34eda7f1ccd277ca013f04b230211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2c0bde0568ff8762e1e633a92f5c94bd0a011a93eaa07fe461914bf51c10a731 0.000600000000 1396731 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": 938669, "vin": [ { "gen": { "height": 938659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c0bde0568ff8762e1e633a92f5c94bd0a011a93eaa07fe461914bf51c10a731" } } ], "extra": [ 1, 145, 41, 248, 29, 23, 206, 217, 223, 55, 243, 217, 69, 5, 254, 218, 12, 208, 153, 150, 243, 78, 218, 127, 28, 205, 39, 124, 160, 19, 240, 75, 35, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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: