Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce5c001a44cae32cf01474ecfaae0af5570c83ec712ce16ec7cd00653d6dae04

Tx prefix hash: b99c946c5aa307b1b7f318a4fd1562c9dcf655cb1c4f8837c39b9732a70bd21f
Tx public key: 572edbcbe214b1e7d4810d8de0124fbbba1352644d56153b9ec6145c8abe749e
Timestamp: 1708298105 Timestamp [UTC]: 2024-02-18 23:15:05 Age [y:d:h:m:s]: 02:277:08:27:20
Block: 960545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 722949 RingCT/type: yes/0
Extra: 01572edbcbe214b1e7d4810d8de0124fbbba1352644d56153b9ec6145c8abe749e02110000000252d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4c4ca2e32ecd78bee56070e94fabd04fa03856ee1e565a1158299892f94b0b1e 0.000600000000 1420116 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": 960555, "vin": [ { "gen": { "height": 960545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c4ca2e32ecd78bee56070e94fabd04fa03856ee1e565a1158299892f94b0b1e" } } ], "extra": [ 1, 87, 46, 219, 203, 226, 20, 177, 231, 212, 129, 13, 141, 224, 18, 79, 187, 186, 19, 82, 100, 77, 86, 21, 59, 158, 198, 20, 92, 138, 190, 116, 158, 2, 17, 0, 0, 0, 2, 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: