Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dcc32710c38f3daa9dea219187ea5349229044beb4b990d18cba0c0a8b09ff7

Tx prefix hash: 5989e0d560fa3c1d51a7c8487a5dc1d7a7030cde3b40fcb23b42474b45891629
Tx public key: c6b22485f3be71fe7636019238aa2d630a71c047e11298b3be3fc376bb205971
Timestamp: 1576644102 Timestamp [UTC]: 2019-12-18 04:41:42 Age [y:d:h:m:s]: 06:340:18:07:23
Block: 28519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1654975 RingCT/type: yes/0
Extra: 01c6b22485f3be71fe7636019238aa2d630a71c047e11298b3be3fc376bb20597102110000001b9159db1e000000000000000000

1 output(s) for total of 0.493748260567 xmr

stealth address amount amount idx tag
00: 120b93ac9d03d95b0e02f8d66d9e38f08058668a48eba915916bd491fedbe97c 0.493748260567 47069 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": 28529, "vin": [ { "gen": { "height": 28519 } } ], "vout": [ { "amount": 493748260567, "target": { "key": "120b93ac9d03d95b0e02f8d66d9e38f08058668a48eba915916bd491fedbe97c" } } ], "extra": [ 1, 198, 178, 36, 133, 243, 190, 113, 254, 118, 54, 1, 146, 56, 170, 45, 99, 10, 113, 192, 71, 225, 18, 152, 179, 190, 63, 195, 118, 187, 32, 89, 113, 2, 17, 0, 0, 0, 27, 145, 89, 219, 30, 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: