Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1881c49536c214ea8f4d854e710679aa79a778c91c9174ee716b2c57cb4102aa

Tx prefix hash: d6798a7dc4e96e946a7d35b21fb7c51097484a28de2fd1241d74d1261dc08511
Tx public key: 9839ac13f171a7e5ad013909eb64d4112803989fa088011aa1ce5898798356e0
Timestamp: 1758163240 Timestamp [UTC]: 2025-09-18 02:40:40 Age [y:d:h:m:s]: 00:340:19:14:01
Block: 1370824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249407 RingCT/type: yes/0
Extra: 019839ac13f171a7e5ad013909eb64d4112803989fa088011aa1ce5898798356e0021100000001b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 02cc6a7b7c6c77f34e14279a7ce4a67dd694f28e0af70e3810804ba768f0d7ab 0.000600000000 1858901 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": 1370834, "vin": [ { "gen": { "height": 1370824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02cc6a7b7c6c77f34e14279a7ce4a67dd694f28e0af70e3810804ba768f0d7ab" } } ], "extra": [ 1, 152, 57, 172, 19, 241, 113, 167, 229, 173, 1, 57, 9, 235, 100, 212, 17, 40, 3, 152, 159, 160, 136, 1, 26, 161, 206, 88, 152, 121, 131, 86, 224, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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: