Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b21ae2c8248a49c0333bf751c8cf3ae576cb949310137064d92f4c4036e09182

Tx prefix hash: cf8c75143bbde5a3af37fd209f41ea45b6d3df464ec44e45b93a734f32c7d1d0
Tx public key: 8f688e369c9a7488e0fe5dfc18dfb3adcb8204930887cba4b96262b2c4f60c26
Timestamp: 1718702675 Timestamp [UTC]: 2024-06-18 09:24:35 Age [y:d:h:m:s]: 02:157:02:11:14
Block: 1046809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636685 RingCT/type: yes/0
Extra: 018f688e369c9a7488e0fe5dfc18dfb3adcb8204930887cba4b96262b2c4f60c2602110000000152d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 52bbf848811ce12af8b0f79251d31608a90490872206d848f0c7ed6ce756ae8d 0.000600000000 1516628 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": 1046819, "vin": [ { "gen": { "height": 1046809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52bbf848811ce12af8b0f79251d31608a90490872206d848f0c7ed6ce756ae8d" } } ], "extra": [ 1, 143, 104, 142, 54, 156, 154, 116, 136, 224, 254, 93, 252, 24, 223, 179, 173, 203, 130, 4, 147, 8, 135, 203, 164, 185, 98, 98, 178, 196, 246, 12, 38, 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: