Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e45ac89ed01fd1e52dfcfbb6002de44396970f38ea8a40adeb77313c51cf88c5

Tx prefix hash: a4109d437b995a18ceb8967c752d1f5840a1d298e538068913f0a1b48d48ba63
Tx public key: 7f6a6d44e9b13758ec29971c6eea85697643e2544fc597816091d8ff9b7a90c7
Timestamp: 1697275517 Timestamp [UCT]: 2023-10-14 09:25:17 Age [y:d:h:m:s]: 01:172:08:44:19
Block: 869359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384204 RingCT/type: yes/0
Extra: 017f6a6d44e9b13758ec29971c6eea85697643e2544fc597816091d8ff9b7a90c7021100000001faf35c9c000000000000000000

1 output(s) for total of 0.808077051000 dcy

stealth address amount amount idx
00: 865664b4ad6da769835a245987465bff0186ea9b151c345ddeaddf9927acc4dc 0.808077051000 1324204 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 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": 869369, "vin": [ { "gen": { "height": 869359 } } ], "vout": [ { "amount": 808077051, "target": { "key": "865664b4ad6da769835a245987465bff0186ea9b151c345ddeaddf9927acc4dc" } } ], "extra": [ 1, 127, 106, 109, 68, 233, 177, 55, 88, 236, 41, 151, 28, 110, 234, 133, 105, 118, 67, 226, 84, 79, 197, 151, 129, 96, 145, 216, 255, 155, 122, 144, 199, 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): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8