Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 955d52bc2d5a0dc52ff2dffcd2880c6ae57bd01ac5605fb857c4a10d8c9d4f8d

Tx prefix hash: d425c3a72cf3139ffb79e556a9028bf0635d414d02c6fe2e5210e3bbd94240c1
Tx public key: 07d1b5dde9d341eb11922cf17339c92370655dbbe0a7bebbe6a71aaab5ec38a2
Timestamp: 1775124223 Timestamp [UTC]: 2026-04-02 10:03:43 Age [y:d:h:m:s]: 00:231:16:34:24
Block: 1511146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171194 RingCT/type: yes/0
Extra: 0107d1b5dde9d341eb11922cf17339c92370655dbbe0a7bebbe6a71aaab5ec38a2021100000001ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f2c0973dfd3bf95b2ea5107c1d38111b2e3f93d96785dadf2011fb677ada00ac 0.000600000000 2000936 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": 1511156, "vin": [ { "gen": { "height": 1511146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2c0973dfd3bf95b2ea5107c1d38111b2e3f93d96785dadf2011fb677ada00ac" } } ], "extra": [ 1, 7, 209, 181, 221, 233, 211, 65, 235, 17, 146, 44, 241, 115, 57, 201, 35, 112, 101, 93, 187, 224, 167, 190, 187, 230, 167, 26, 170, 181, 236, 56, 162, 2, 17, 0, 0, 0, 1, 238, 75, 113, 129, 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: