Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffe093732704e8493de923c7c066a817e1a27431987bdcfea1694b2b7739d336

Tx prefix hash: 322170e65e24049c627552019d02cdbbab1ab64e525c37e135acf8be1a140ad7
Tx public key: 3d47a59691b8606f96bd010dea5646f2a602e3c5cb49d20294d67a72d8442be1
Timestamp: 1722963298 Timestamp [UCT]: 2024-08-06 16:54:58 Age [y:d:h:m:s]: 00:168:22:40:50
Block: 1082119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120824 RingCT/type: yes/0
Extra: 013d47a59691b8606f96bd010dea5646f2a602e3c5cb49d20294d67a72d8442be1021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2810a55f9def6b705ea8347b93f676d2775bc58246ae0ec3866d2fcaafdcf482 0.600000000000 1555942 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 dinasty-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": 1082129, "vin": [ { "gen": { "height": 1082119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2810a55f9def6b705ea8347b93f676d2775bc58246ae0ec3866d2fcaafdcf482" } } ], "extra": [ 1, 61, 71, 165, 150, 145, 184, 96, 111, 150, 189, 1, 13, 234, 86, 70, 242, 166, 2, 227, 197, 203, 73, 210, 2, 148, 214, 122, 114, 216, 68, 43, 225, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8