Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5a86d8041370737fa52aaae8b379eddadcd25c7c67eb5866ea1b5399c66e45c

Tx prefix hash: 75bc9374add46bfa98b31fc0ff2529ff723d0ec94ad3f2e681c6b7f2bf113db9
Tx public key: 8f5d6420f0d93e9aae331ba26aec1bcad41686b5c949e1c21cd3fda205cde740
Timestamp: 1694353850 Timestamp [UCT]: 2023-09-10 13:50:50 Age [y:d:h:m:s]: 01:140:05:53:33
Block: 845118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361318 RingCT/type: yes/0
Extra: 018f5d6420f0d93e9aae331ba26aec1bcad41686b5c949e1c21cd3fda205cde740021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.972239596000 dcy

stealth address amount amount idx
00: 68ab24694b25ee69568f59e2bb82ed2663b8c4ef37194166cabf0890f9432a37 0.972239596000 1298474 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": 845128, "vin": [ { "gen": { "height": 845118 } } ], "vout": [ { "amount": 972239596, "target": { "key": "68ab24694b25ee69568f59e2bb82ed2663b8c4ef37194166cabf0890f9432a37" } } ], "extra": [ 1, 143, 93, 100, 32, 240, 217, 62, 154, 174, 51, 27, 162, 106, 236, 27, 202, 212, 22, 134, 181, 201, 73, 225, 194, 28, 211, 253, 162, 5, 205, 231, 64, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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