Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa502b538b083bbe7fc8c2c44ceff2687c23e1876c44d06869f6a5265bb66578

Tx prefix hash: 49e24649de75371e02459817c5d25bbc70f2e85e19feba47499806eef37013b4
Tx public key: dcc676295a077b784123a16bd97fc6ef7b9c951f56a49b8bde0a090986aa74b8
Timestamp: 1707663728 Timestamp [UTC]: 2024-02-11 15:02:08 Age [y:d:h:m:s]: 02:284:08:56:05
Block: 955272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 728222 RingCT/type: yes/0
Extra: 01dcc676295a077b784123a16bd97fc6ef7b9c951f56a49b8bde0a090986aa74b802110000000152d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 52b1e3d183be0336c7faeae629e5313f4e9b52001da98c6313cd05305ac97272 0.000600000000 1414558 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": 955282, "vin": [ { "gen": { "height": 955272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52b1e3d183be0336c7faeae629e5313f4e9b52001da98c6313cd05305ac97272" } } ], "extra": [ 1, 220, 198, 118, 41, 90, 7, 123, 120, 65, 35, 161, 107, 217, 127, 198, 239, 123, 156, 149, 31, 86, 164, 155, 139, 222, 10, 9, 9, 134, 170, 116, 184, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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: