Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00a2125b99edaabc241d780f449dc289436c49766338139ea6e038d934d8170f

Tx prefix hash: 469d0eb5948d7c1789481335c680be1154a048b5638fe2e3840183cabf26e702
Tx public key: c3724be5da7adc147bca62b371c142584bba0ddc96b6cc502d5f85bec10a2d47
Timestamp: 1673971518 Timestamp [UTC]: 2023-01-17 16:05:18 Age [y:d:h:m:s]: 03:307:21:49:49
Block: 676821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1005917 RingCT/type: yes/0
Extra: 01c3724be5da7adc147bca62b371c142584bba0ddc96b6cc502d5f85bec10a2d470211000000058b7b6602000000000000000000

1 output(s) for total of 0.003510839796 xmr

stealth address amount amount idx tag
00: c9dafc99bae859310f331f7f38c3e233ea46d7cc19cca75a08834ec000a19393 0.003510839796 1118566 of 0 -

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": 676831, "vin": [ { "gen": { "height": 676821 } } ], "vout": [ { "amount": 3510839796, "target": { "key": "c9dafc99bae859310f331f7f38c3e233ea46d7cc19cca75a08834ec000a19393" } } ], "extra": [ 1, 195, 114, 75, 229, 218, 122, 220, 20, 123, 202, 98, 179, 113, 193, 66, 88, 75, 186, 13, 220, 150, 182, 204, 80, 45, 95, 133, 190, 193, 10, 45, 71, 2, 17, 0, 0, 0, 5, 139, 123, 102, 2, 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: