Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40d92c7d4a2ca4a33fa7e165358d6bdaff88dddf773b69aef616d78df6713321

Tx prefix hash: c52e9cb3129b77a683281548975d694fcf804bffc0c0b722dec71705ca976ebb
Tx public key: 6504263950233e08cb8196f607cd2b770d78fe322e81ea0d52cbf9e751b2a205
Timestamp: 1773846361 Timestamp [UTC]: 2026-03-18 15:06:01 Age [y:d:h:m:s]: 00:241:17:01:35
Block: 1500562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178193 RingCT/type: yes/0
Extra: 016504263950233e08cb8196f607cd2b770d78fe322e81ea0d52cbf9e751b2a205021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 248d760647f7f3719ff89b8c2bc21065961113b2c1e5b2d31fa487be07e4d430 0.000600000000 1990236 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": 1500572, "vin": [ { "gen": { "height": 1500562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "248d760647f7f3719ff89b8c2bc21065961113b2c1e5b2d31fa487be07e4d430" } } ], "extra": [ 1, 101, 4, 38, 57, 80, 35, 62, 8, 203, 129, 150, 246, 7, 205, 43, 119, 13, 120, 254, 50, 46, 129, 234, 13, 82, 203, 249, 231, 81, 178, 162, 5, 2, 17, 0, 0, 0, 7, 241, 136, 200, 168, 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: