Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71cb39c662693c1daa109897578125434eec2239dea5d6ccccb8a4d2fe52abe7

Tx prefix hash: 515267af275866fb33d02e9853c93cbf21d4c445ec90201486a443323582901a
Tx public key: 4283f1738d7cc11c3c030d8c6dd9c58fedf079c8c5e5cbf0a2362e3c535bc706
Timestamp: 1699133833 Timestamp [UTC]: 2023-11-04 21:37:13 Age [y:d:h:m:s]: 02:188:13:27:55
Block: 884821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 646708 RingCT/type: yes/0
Extra: 014283f1738d7cc11c3c030d8c6dd9c58fedf079c8c5e5cbf0a2362e3c535bc706021100000001faf35c9c000000000000000000

1 output(s) for total of 0.000718159196 xmr

stealth address amount amount idx tag
00: 5d8feacd1dc52fd28fa0c882769d6cd6c6ba4fe78b92f13ea9a22dabed67e054 0.000718159196 1340570 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": 884831, "vin": [ { "gen": { "height": 884821 } } ], "vout": [ { "amount": 718159196, "target": { "key": "5d8feacd1dc52fd28fa0c882769d6cd6c6ba4fe78b92f13ea9a22dabed67e054" } } ], "extra": [ 1, 66, 131, 241, 115, 141, 124, 193, 28, 60, 3, 13, 140, 109, 217, 197, 143, 237, 240, 121, 200, 197, 229, 203, 240, 162, 54, 46, 60, 83, 91, 199, 6, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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: