Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ffd947d853238a1a74bfb143503aeeb93cdd02eaa3d1625fd7658f96b93c7bb

Tx prefix hash: 3c3b87a91c44f37b14c241692a2484407924eec94c7460a469da2efa60a0d5a4
Tx public key: 444b7df07545b042d3a2d2edc7d9f12531de1c1cce003c83273470ab4c652887
Timestamp: 1741961990 Timestamp [UTC]: 2025-03-14 14:19:50 Age [y:d:h:m:s]: 01:251:02:46:29
Block: 1239177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443668 RingCT/type: yes/0
Extra: 01444b7df07545b042d3a2d2edc7d9f12531de1c1cce003c83273470ab4c652887021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 88c473731ca9c3055b2621e9d6cc39a143efbaf44f39a9a3251d2cc3fd484e14 0.000600000000 1726142 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": 1239187, "vin": [ { "gen": { "height": 1239177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88c473731ca9c3055b2621e9d6cc39a143efbaf44f39a9a3251d2cc3fd484e14" } } ], "extra": [ 1, 68, 75, 125, 240, 117, 69, 176, 66, 211, 162, 210, 237, 199, 217, 241, 37, 49, 222, 28, 28, 206, 0, 60, 131, 39, 52, 112, 171, 76, 101, 40, 135, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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: