Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58248af6d046981063e6b1efcdfba98bc86eabe65484a543d03b82d0df4ed977

Tx prefix hash: cab86b8141136df242f7dcf2b80e82288da9ceb7dc3414fa10f2015faad5d91b
Tx public key: 0db8cbb95b52b9d3f9c14932ab579f30757069f9d1c7b5ad583748a552540ac9
Timestamp: 1579576440 Timestamp [UTC]: 2020-01-21 03:14:00 Age [y:d:h:m:s]: 06:303:15:15:28
Block: 49862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1631449 RingCT/type: yes/0
Extra: 010db8cbb95b52b9d3f9c14932ab579f30757069f9d1c7b5ad583748a552540ac9021100000008dcee4b4d000000000000000000

1 output(s) for total of 0.419553480746 xmr

stealth address amount amount idx tag
00: 2837aae9f8be9cc7a5eaa66ea9abfa0e942ada6ce2b6f5ede3516dd787063b64 0.419553480746 92574 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": 49872, "vin": [ { "gen": { "height": 49862 } } ], "vout": [ { "amount": 419553480746, "target": { "key": "2837aae9f8be9cc7a5eaa66ea9abfa0e942ada6ce2b6f5ede3516dd787063b64" } } ], "extra": [ 1, 13, 184, 203, 185, 91, 82, 185, 211, 249, 193, 73, 50, 171, 87, 159, 48, 117, 112, 105, 249, 209, 199, 181, 173, 88, 55, 72, 165, 82, 84, 10, 201, 2, 17, 0, 0, 0, 8, 220, 238, 75, 77, 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: